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=145490
Your paranoid android.
=== w10pro64_ja (64 bit report) ===
user32: input.c:638: Test failed: peek: rctrl_scan: 2: test->expect 0: got LL_HOOK_KEYBD msg WM_KEYDOWN scan 0x1d, vkey 0x19, flags 0x11, extra 0 input.c:638: Test failed: peek: rctrl_scan: 2: test->expect 1: got MSG_TEST_WIN hwnd 0000000000000000, msg WM_KEYDOWN, wparam 0xe5, lparam 0x11d0001 input.c:638: Test failed: peek: rctrl_scan: 2: test->expect 2 (spurious): got MSG_TEST_WIN hwnd 0000000000000000, msg WM_KEYDOWN, wparam 0x19, lparam 0x11d0001 input.c:639: Test failed: peek: rctrl_scan: 2: got VK_CONTROL: 0x1 input.c:639: Test failed: peek: rctrl_scan: 2: got 0x19: 0x81 input.c:639: Test failed: peek: rctrl_scan: 2: got VK_RCONTROL: 0 input.c:638: Test failed: peek: rctrl_scan: 3: test->expect 0: got LL_HOOK_KEYBD msg WM_KEYUP scan 0x1d, vkey 0x19, flags 0x91, extra 0 input.c:638: Test failed: peek: rctrl_scan: 3: test->expect 1: got MSG_TEST_WIN hwnd 0000000000000000, msg WM_KEYUP, wparam 0x19, lparam 0xc11d0001 input.c:638: Test failed: receive: rctrl_scan: 2: test->expect 0: got LL_HOOK_KEYBD msg WM_KEYDOWN scan 0x1d, vkey 0x19, flags 0x11, extra 0 input.c:638: Test failed: receive: rctrl_scan: 2: test->expect 1: got MSG_TEST_WIN hwnd 0000000000000000, msg WM_KEYDOWN, wparam 0xe5, lparam 0x11d0001 input.c:638: Test failed: receive: rctrl_scan: 2: test->expect 2 (spurious): got MSG_TEST_WIN hwnd 0000000000000000, msg WM_KEYDOWN, wparam 0x19, lparam 0x11d0001 input.c:639: Test failed: receive: rctrl_scan: 2: got VK_CONTROL: 0x1 input.c:639: Test failed: receive: rctrl_scan: 2: got 0x19: 0x81 input.c:639: Test failed: receive: rctrl_scan: 2: got VK_RCONTROL: 0 input.c:638: Test failed: receive: rctrl_scan: 3: test->expect 0: got LL_HOOK_KEYBD msg WM_KEYUP scan 0x1d, vkey 0x19, flags 0x91, extra 0 input.c:638: Test failed: receive: rctrl_scan: 3: test->expect 1: got MSG_TEST_WIN hwnd 0000000000000000, msg WM_KEYUP, wparam 0x19, lparam 0xc11d0001
=== debian11 (32 bit zh:CN report) ===
user32: input.c:638: Test failed: peek: rshift_scan: 1: test->expect 2: got MSG_TEST_WIN hwnd 00000000, msg WM_CHAR, wparam 0x46, lparam 0x210001 input.c:638: Test failed: receive: rshift_scan: 1: test->expect 2: got MSG_TEST_WIN hwnd 00000000, msg WM_CHAR, wparam 0x46, lparam 0x210001
=== debian11b (64 bit WoW report) ===
dinput: joystick8.c:5759: Test failed: input 1: WaitForSingleObject returned 0x102 joystick8.c:5760: Test failed: input 1: got 0 WM_INPUT messages joystick8.c:5763: Test failed: input 1: got dwType 0 joystick8.c:5764: Test failed: input 1: got header.dwSize 0 joystick8.c:5766: Test failed: input 1: got hDevice 0000000000000000 joystick8.c:5768: Test failed: input 1: got dwSizeHid 0 joystick8.c:5769: Test failed: input 1: got dwCount 0