Hi,
It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated.
The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details:
The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120465
Your paranoid android.
=== w1064v1507 (32 bit report) ===
d3d8: device.c:10825: Test failed: Adapter 0: SetForegroundWindow failed, error 0.
=== w1064v1809 (32 bit report) ===
d3d8: device.c:10825: Test failed: Adapter 0: SetForegroundWindow failed, error 0.
=== w10pro64 (32 bit report) ===
d3d8: device.c:10825: Test failed: Adapter 0: SetForegroundWindow failed, error 0.
=== debian11 (32 bit report) ===
d3d8: Unhandled exception: page fault on read access to 0x007b1000 in 32-bit code (0x714b859f).
=== debian11 (32 bit German report) ===
d3d8: Unhandled exception: page fault on read access to 0x002f0010 in 32-bit code (0x714b859f).
=== debian11 (32 bit French report) ===
d3d8: Unhandled exception: page fault on read access to 0x002f0010 in 32-bit code (0x714b859f).
=== debian11 (32 bit Chinese:China report) ===
d3d8: Unhandled exception: page fault on read access to 0x002f0010 in 32-bit code (0x714b859f).
=== debian11 (64 bit WoW report) ===
d3d8: Unhandled exception: page fault on read access to 0xffffffffffffffff in 64-bit code (0x000000712b2dce).
-
Marvin