On 19 April 2013 16:22, Brian Paul wrote:
> On 04/19/2013 04:33 AM, Jose Fonseca wrote:
>>
>> Yes, assuming stderr messages are driver warnings seems a bit pedantic.
>>
>> We could do the other way around -- have a whitelist of warning regular
>> expressions that we do known that are worrisome.
>
On Fri, Apr 19, 2013 at 9:22 AM, Brian Paul wrote:
> On 04/19/2013 04:33 AM, Jose Fonseca wrote:
>>
>> Yes, assuming stderr messages are driver warnings seems a bit pedantic.
>>
>> We could do the other way around -- have a whitelist of warning regular
>> expressions that we do known that are worr
On 04/19/2013 04:33 AM, Jose Fonseca wrote:
Yes, assuming stderr messages are driver warnings seems a bit pedantic.
We could do the other way around -- have a whitelist of warning regular
expressions that we do known that are worrisome.
Yeah, that's an idea. But I think the only ones that co
Yes, assuming stderr messages are driver warnings seems a bit pedantic.
We could do the other way around -- have a whitelist of warning regular
expressions that we do known that are worrisome.
Jose
- Original Message -
> Normally, if anything unexpected is printed to stderr we report 'w
Normally, if anything unexpected is printed to stderr we report 'warn'
for the test result. The list of expected/allowed stderr message is
found at the end of core.py. It's a PITA to update this list and if
you've temporarily inserted extra debug code in Mesa/gallium it causes
piglit to just repo
