Re: [PATCH 1/5] d3d9/tests: Use a separate device for test_vshader_input().

[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://newtestbot.winehq.org/JobDetails.pl?Key=5937

Your paranoid android.

=== w8 (32 bit visual) ===
visual.c:7297: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00
visual.c:7282: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00
visual.c:7282: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00

[PATCH 1/5] d3d9/tests: Use a separate device for test_vshader_input().

[Henri Verbeet]

On 25 March 2014 09:50, Marvin  wrote:
> === w8 (32 bit visual) ===
> visual.c:7297: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00
> visual.c:7282: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00
> visual.c:7282: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00

This looks at least somewhat like a legitimate failure, so I think
it's best to ignore this series for the moment.