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=147985
Your paranoid android.
=== debian11 (32 bit report) ===
mlang: mlang.c:657: Test failed: expected lenA 6, got 7 mlang.c:660: Test failed: bufW/stringW mismatch
=== debian11 (32 bit ar:MA report) ===
mlang: mlang.c:657: Test failed: expected lenA 6, got 7 mlang.c:660: Test failed: bufW/stringW mismatch
=== debian11 (32 bit de report) ===
mlang: mlang.c:657: Test failed: expected lenA 6, got 7 mlang.c:660: Test failed: bufW/stringW mismatch
=== debian11 (32 bit fr report) ===
mlang: mlang.c:657: Test failed: expected lenA 6, got 7 mlang.c:660: Test failed: bufW/stringW mismatch
=== debian11 (32 bit he:IL report) ===
mlang: mlang.c:657: Test failed: expected lenA 6, got 7 mlang.c:660: Test failed: bufW/stringW mismatch
=== debian11 (32 bit hi:IN report) ===
mlang: mlang.c:657: Test failed: expected lenA 6, got 7 mlang.c:660: Test failed: bufW/stringW mismatch
=== debian11 (32 bit ja:JP report) ===
mlang: mlang.c:657: Test failed: expected lenA 6, got 7 mlang.c:660: Test failed: bufW/stringW mismatch
=== debian11b (32 bit WoW report) ===
mlang: mlang.c:657: Test failed: expected lenA 6, got 7 mlang.c:660: Test failed: bufW/stringW mismatch
=== debian11b (64 bit WoW report) ===
mlang: mlang.c:657: Test failed: expected lenA 6, got 7 mlang.c:660: Test failed: bufW/stringW mismatch
user32: input.c:4305: Test succeeded inside todo block: button_down_hwnd_todo 1: got MSG_TEST_WIN hwnd 00000000009400EA, msg WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032