Re: [PATCH 2/5] ddraw/tests: Don't require a 3D device for test_resource_priority().

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

Your paranoid android.

=== w1064 (32 bit ddraw7) ===
ddraw7.c:2253: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}.