Re: [PATCH 4/5] ddraw/tests: Don't trust what EnumDevices() tells us about the supported Z buffer formats.

[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=5274

Your paranoid android.

=== w8 (32 bit ddraw2) ===
ddraw2.c:746: Test failed: Got unexpected color 0x00000000.
ddraw2.c:3199: Test failed: Got unexpected color 0x000000ff.
Failure running script in VM: network read timed out

=== w8 (32 bit ddraw1) ===
ddraw1.c:783: Test failed: Got unexpected color 0x00000000.
ddraw1.c:1297: Test failed: Expected color 0x00ff0000 for test 0, got 0x0000ff00.
ddraw1.c:1319: Test failed: Expected color 0x000000ff for test 0, got 0x0000ff00.
ddraw1.c:1297: Test failed: Expected color 0x00ff0000 for test 1, got 0x0000ff00.
ddraw1.c:1319: Test failed: Expected color 0x000000ff for test 1, got 0x0000ff00.
ddraw1.c:2909: Test failed: Got unexpected color 0x000000ff.
ddraw1.c:4103: Test failed: Got unexpected refcount 3.
ddraw1.c:4122: Test failed: Got unexpected refcount 3.
ddraw1.c:4129: Test failed: Got unexpected hr 0.
ddraw1.c:4132: Test failed: Got unexpected refcount 3.
ddraw1.c:4134: Test failed: Got unexpected refcount 2.
ddraw1.c:4140: Test failed: Got unexpected hr 0.
ddraw1.c:4143: Test failed: Got unexpected refcount 2.
ddraw1.c:4145: Test failed: Got unexpected refcount 1.