Re: [PATCH 1/2] ddraw/tests: Try to avoid killing the Intel (kernel) driver.

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

Your paranoid android.


=== w1064 (32 bit ddraw2) ===
ddraw2.c:2445: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).

=== w1064 (64 bit ddraw2) ===
ddraw2.c:2445: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).

=== w1064 (32 bit ddraw1) ===
ddraw1.c:2294: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).

=== w1064 (64 bit ddraw1) ===
ddraw1.c:2294: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).

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

=== w1064 (64 bit ddraw7) ===
ddraw7.c:2314: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).

=== w1064 (32 bit ddraw4) ===
ddraw4.c:2588: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).

=== w1064 (64 bit ddraw4) ===
ddraw4.c:2588: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).