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=148767
Your paranoid android.
=== w11pro64_amd (64 bit report) ===
user32: input.c:4260: Test failed: button_down_hwnd 0: got MSG_TEST_WIN hwnd 0000000000050076, msg WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032 input.c:4260: Test failed: button_down_hwnd 1 (missing): MSG_TEST_WIN hwnd 0000000000050076, WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032 input.c:4305: Test failed: button_down_hwnd_todo 1 (missing): MSG_TEST_WIN hwnd 0000000000050076, WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032 input.c:4309: Test failed: button_up_hwnd 1: got MSG_TEST_WIN hwnd 0000000000050076, msg WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032 input.c:4309: Test failed: button_up_hwnd 2 (spurious): got MSG_TEST_WIN hwnd 0000000000050076, msg WM_LBUTTONUP, wparam 0, lparam 0x320032
=== debian11 (32 bit he:IL report) ===
user32: input.c:4305: Test succeeded inside todo block: button_down_hwnd_todo 1: got MSG_TEST_WIN hwnd 000400A0, msg WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032