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=125412
Your paranoid android.
=== debian11 (32 bit report) ===
gdiplus: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x64a952d5).
=== debian11 (32 bit ar:MA report) ===
gdiplus: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x64a952d5).
=== debian11 (32 bit de report) ===
gdiplus: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x64a952d5).
=== debian11 (32 bit fr report) ===
gdiplus: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x64a952d5).
=== debian11 (32 bit he:IL report) ===
gdiplus: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x64a952d5).
=== debian11 (32 bit hi:IN report) ===
gdiplus: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x64a952d5).
=== debian11 (32 bit ja:JP report) ===
gdiplus: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x64a952d5).
=== debian11 (32 bit zh:CN report) ===
gdiplus: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x64a952d5).
=== debian11 (32 bit WoW report) ===
gdiplus: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x64a952d5).
=== debian11 (64 bit WoW report) ===
gdiplus: Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x000000648968dd).