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=147515
Your paranoid android.
=== debian11 (32 bit report) ===
comctl32: taskdialog.c:725: Test succeeded inside todo block: Expect state: 3 got state: 3 taskdialog.c:727: Test succeeded inside todo block: Expect state: 2 got state: 2 taskdialog.c:725: Test succeeded inside todo block: Expect state: 3 got state: 3 taskdialog.c:727: Test succeeded inside todo block: Expect state: 2 got state: 2 taskdialog.c:725: Test succeeded inside todo block: Expect state: 3 got state: 3 taskdialog.c:727: Test succeeded inside todo block: Expect state: 2 got state: 2
=== debian11b (64 bit WoW report) ===
comctl32: taskdialog.c:725: Test succeeded inside todo block: Expect state: 3 got state: 3 taskdialog.c:727: Test succeeded inside todo block: Expect state: 2 got state: 2 taskdialog.c:725: Test succeeded inside todo block: Expect state: 3 got state: 3 taskdialog.c:727: Test succeeded inside todo block: Expect state: 2 got state: 2 taskdialog.c:725: Test succeeded inside todo block: Expect state: 3 got state: 3 taskdialog.c:727: Test succeeded inside todo block: Expect state: 2 got state: 2
user32: input.c:4305: Test succeeded inside todo block: button_down_hwnd_todo 1: got MSG_TEST_WIN hwnd 00000000006000FC, msg WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032