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=149886
Your paranoid android.
=== debian11 (32 bit report) ===
timeout.exe: timeout.c:129: Test failed: Expected exitcode 1, got c000013a
=== debian11 (32 bit ar:MA report) ===
timeout.exe: timeout.c:129: Test failed: Expected exitcode 1, got c000013a
=== debian11 (32 bit de report) ===
timeout.exe: timeout.c:129: Test failed: Expected exitcode 1, got c000013a
=== debian11 (32 bit fr report) ===
timeout.exe: timeout.c:129: Test failed: Expected exitcode 1, got c000013a
=== debian11 (32 bit he:IL report) ===
timeout.exe: timeout.c:129: Test failed: Expected exitcode 1, got c000013a
=== debian11 (32 bit hi:IN report) ===
timeout.exe: timeout.c:129: Test failed: Expected exitcode 1, got c000013a
=== debian11 (32 bit ja:JP report) ===
timeout.exe: timeout.c:129: Test failed: Expected exitcode 1, got c000013a
=== debian11 (32 bit zh:CN report) ===
timeout.exe: timeout.c:129: Test failed: Expected exitcode 1, got c000013a
=== debian11b (32 bit WoW report) ===
timeout.exe: timeout.c:129: Test failed: Expected exitcode 1, got c000013a
=== debian11b (64 bit WoW report) ===
timeout.exe: timeout.c:129: Test failed: Expected exitcode 1, got c000013a
user32: input.c:4305: Test succeeded inside todo block: button_down_hwnd_todo 1: got MSG_TEST_WIN hwnd 0000000000A200DC, msg WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032 win.c:4070: Test failed: Expected active window 0000000004330158, got 0000000000000000. win.c:4071: Test failed: Expected focus window 0000000004330158, got 0000000000000000.