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=117153
Your paranoid android.
=== w10pro64 (32 bit report) ===
user32: msg.c:13238: Test failed: message time not advanced: c4c7 c4c7 msg.c:13239: Test failed: coords not changed: (101 101) (101 101) msg.c:13256: Test failed: message time not advanced: c4c7 c4c7 msg.c:13257: Test failed: coords not changed: (101 101) (101 101)
=== w10pro64_en_AE_u8 (64 bit report) ===
user32: msg.c:13238: Test failed: message time not advanced: 155ac 155ac msg.c:13239: Test failed: coords not changed: (101 101) (101 101) msg.c:13256: Test failed: message time not advanced: 155ac 155ac msg.c:13257: Test failed: coords not changed: (101 101) (101 101)
=== debian11 (32 bit German report) ===
user32: msg.c:18882: Test succeeded inside todo block: wrong status 00000000 msg.c:18886: Test succeeded inside todo block: SendMessage from other thread 5: marked "todo_wine" but succeeds
=== debian11 (32 bit Hindi:India report) ===
user32: msg.c:18854: Test succeeded inside todo block: SendMessage from other thread 1: marked "todo_wine" but succeeds msg.c:18858: Test succeeded inside todo block: WaitForSingleObject failed, ret:0 msg.c:18874: Test succeeded inside todo block: SendMessage from other thread 3: marked "todo_wine" but succeeds msg.c:18882: Test succeeded inside todo block: wrong status 00000000 msg.c:18886: Test succeeded inside todo block: SendMessage from other thread 5: marked "todo_wine" but succeeds