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=132312
Your paranoid android.
=== debian11b (64 bit WoW report) ===
imm32: imm32.c:7092: Test failed: kbd_char_first: 4 (spurious): got hkl FFFFFFFFE020047F, himc 0000000000020074, IME_SET_ACTIVE_CONTEXT flag 0 imm32.c:7092: Test failed: kbd_char_first: 5 (spurious): got hkl FFFFFFFFE020047F, himc 0000000000020074, MSG_TEST_WIN msg 0x281, wparam 0, lparam 0xc000000f imm32.c:7092: Test failed: kbd_char_first: 6 (spurious): got hkl FFFFFFFFE020047F, himc 0000000000020074, MSG_IME_UI msg 0x281, wparam 0, lparam 0xc000000f imm32.c:7092: Test failed: kbd_char_first: 7 (spurious): got hkl FFFFFFFFE020047F, himc 0000000000020074, IME_SET_ACTIVE_CONTEXT flag 1 imm32.c:7092: Test failed: kbd_char_first: 8 (spurious): got hkl FFFFFFFFE020047F, himc 0000000000020074, MSG_TEST_WIN msg 0x281, wparam 0x1, lparam 0xc000000f imm32.c:7092: Test failed: kbd_char_first: 9 (spurious): got hkl FFFFFFFFE020047F, himc 0000000000020074, MSG_IME_UI msg 0x281, wparam 0x1, lparam 0xc000000f