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=143146
Your paranoid android.
=== w10pro64_en_AE_u8 (32 bit report) ===
user32: input.c:3358: Test failed: 04094c09 / 04110411: WaitForSingleObject returned 0x102 input.c:3381: Test failed: 04094c09 / 04110411: got change_hkl 00000000 input.c:3386: Test failed: 04094c09 / 04110411: got tmp_layout 04110411
=== w11pro64 (32 bit report) ===
user32: input.c:4064: Test failed: button_up_hwnd 0: got MSG_TEST_WIN hwnd 00050040, msg WM_LBUTTONUP, wparam 0, lparam 0x320032 input.c:4064: Test failed: button_up_hwnd 1 (missing): MSG_TEST_WIN hwnd 00050040, WM_LBUTTONUP, wparam 0, lparam 0x320032
=== debian11 (32 bit fr report) ===
user32: input.c:3902: Test succeeded inside todo block: button_down_hwnd_todo 1: got MSG_TEST_WIN hwnd 0007004A, msg WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032
=== debian11 (32 bit ja:JP report) ===
user32: input.c:3902: Test succeeded inside todo block: button_down_hwnd_todo 1: got MSG_TEST_WIN hwnd 0007004A, msg WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032