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=142356
Your paranoid android.
=== w10pro64_ja (64 bit report) ===
user32: input.c:3240: Test failed: 04110411 / 04110411: got change_hkl 0000000004110411
=== w10pro64_zh_CN (64 bit report) ===
user32: input.c:3240: Test failed: 08040804 / 08040804: got change_hkl 0000000008040804
=== debian11 (32 bit zh:CN report) ===
user32: input.c:592: Test failed: peek: lmenu_vkey_peeked: 1: test->expect 2: got MSG_TEST_WIN hwnd 00000000, msg WM_SYSCHAR, wparam 0x66, lparam 0x20020001 input.c:592: Test failed: peek: shift_vkey: 1: test->expect 2: got MSG_TEST_WIN hwnd 00000000, msg WM_CHAR, wparam 0x46, lparam 0x20001 input.c:592: Test failed: receive: lmenu_vkey: 1: test->expect 2: got MSG_TEST_WIN hwnd 00000000, msg WM_SYSCHAR, wparam 0x66, lparam 0x20020001 input.c:592: Test failed: receive: lmenu_vkey: 1: test->expect 3: got MSG_TEST_WIN hwnd 00000000, msg WM_SYSCOMMAND, wparam 0xf100, lparam 0x66 input.c:592: Test failed: receive: shift_vkey: 1: test->expect 2: got MSG_TEST_WIN hwnd 00000000, msg WM_CHAR, wparam 0x46, lparam 0x20001