Re: [PATCH v2 5/5] d3d8/tests: Uninitialized varyings tests.

[Marvin]

Hi,

While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://testbot.winehq.org/JobDetails.pl?Key=17302

Your paranoid android.

=== w1064 (32 bit visual) ===
visual.c:8250: Test failed: Got unexpected color 0xffffffff, case 3.
visual.c:8250: Test failed: Got unexpected color 0x00800000, case 5.
visual.c:8250: Test failed: Got unexpected color 0x00800000, case 6.

[PATCH v2 5/5] d3d8/tests: Uninitialized varyings tests.

[Matteo Bruni]

2015-10-12 23:58 GMT+02:00 Marvin :
> Hi,
>
> While running your changed tests on Windows, I think I found new failures.
> Being a bot and all I'm not very good at pattern recognition, so I might be
> wrong, but could you please double-check?
> Full results can be found at
> https://testbot.winehq.org/JobDetails.pl?Key=17302
>
> Your paranoid android.
>
> === w1064 (32 bit visual) ===
> visual.c:8250: Test failed: Got unexpected color 0xffffffff, case 3.
> visual.c:8250: Test failed: Got unexpected color 0x00800000, case 5.
> visual.c:8250: Test failed: Got unexpected color 0x00800000, case 6.

The log suggests that specific VM has, for some reason, a different
adapter description string ("Red Hat QXL controller") compared to the
others so the WARP check fails.
I guess I'll spend some time figuring out a better way to detect WARP
in the d3d8 tests.