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=148876
Your paranoid android.
=== w7u_el (32 bit report) ===
dplayx: dplayx.c:2345: Test failed: got flags 0.
=== w10pro64 (32 bit report) ===
dplayx: dplayx.c:2954: Test failed: select() returned 1.
=== debian11 (32 bit hi:IN report) ===
dplayx: dplayx.c:2366: Test failed: got mixed 0xfab00086. dplayx.c:2366: Test failed: recv() returned 6. dplayx.c:2366: Test failed: got password L"". dplayx.c:2366: Test failed: recv() returned -1. dplayx.c:2366: Test failed: got tick count 0xcccccccc.
=== debian11b (64 bit WoW report) ===
kernel32: comm.c:1574: Test failed: AbortWaitCts hComPortEvent failed comm.c:1586: Test failed: Unexpected time 1001, expected around 500
user32: input.c:4305: Test succeeded inside todo block: button_down_hwnd_todo 1: got MSG_TEST_WIN hwnd 0000000000C700EA, msg WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032