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=148322
Your paranoid android.
=== w1064v1507 (32 bit report) ===
mlang: mlang.c:2791: Test failed: IMLangFontLink2_MapFont: expected S_OK/128/1, got 8a1503e9/0/0 mlang.c:2796: Test failed: IMLangFontLink2_ReleaseFont: expected S_OK, got 80004005 mlang.c:2802: Test failed: MapFont() failed, hr 0x80004005. mlang.c:2805: Test failed: expected !NULL/!NULL, got 00000000/250A0529 mlang.c:2806: Test failed: expected equal, got not equal mlang.c:2809: Test failed: code pages of font is incorrect
=== w1064v1507 (64 bit report) ===
mlang: mlang.c:2791: Test failed: IMLangFontLink2_MapFont: expected S_OK/128/1, got 8a1503e9/0/0 mlang.c:2796: Test failed: IMLangFontLink2_ReleaseFont: expected S_OK, got 80004005 mlang.c:2802: Test failed: MapFont() failed, hr 0x80004005. mlang.c:2805: Test failed: expected !NULL/!NULL, got 0000000000000000/00000000250A0529 mlang.c:2806: Test failed: expected equal, got not equal mlang.c:2809: Test failed: code pages of font is incorrect
=== debian11b (64 bit WoW report) ===
user32: input.c:4305: Test succeeded inside todo block: button_down_hwnd_todo 1: got MSG_TEST_WIN hwnd 0000000001CE00F4, msg WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032