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=136614
Your paranoid android.
=== debian11 (32 bit report) ===
mf: mf.c:1839: Test failed: Unexpected call.
=== debian11 (32 bit ar:MA report) ===
mf: mf.c:1839: Test failed: Unexpected call.
=== debian11 (32 bit de report) ===
mf: mf.c:1839: Test failed: Unexpected call. mf.c:5562: Test failed: WaitForSingleObject returned 258 mf.c:5562: Test failed: Unexpected hr 0xd36d8. Unhandled exception: page fault on execute access to 0x00000000 in 32-bit code (0x00000000).
=== debian11 (32 bit fr report) ===
mf: mf.c:1839: Test failed: Unexpected call.
=== debian11 (32 bit he:IL report) ===
mf: mf.c:1839: Test failed: Unexpected call.
=== debian11 (32 bit hi:IN report) ===
mf: mf.c:1839: Test failed: Unexpected call.
=== debian11 (32 bit ja:JP report) ===
mf: mf.c:1839: Test failed: Unexpected call.
=== debian11 (32 bit zh:CN report) ===
mf: mf.c:1839: Test failed: Unexpected call.
=== debian11b (32 bit WoW report) ===
mf: mf.c:1839: Test failed: Unexpected call.
=== debian11b (64 bit WoW report) ===
mf: mf.c:1839: Test failed: Unexpected call.