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=151211
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
kernel32: loader.c:2297: Test failed: 0: wrong alignment 001845E8
=== w7u_adm (32 bit report) ===
kernel32: loader.c:2297: Test failed: 0: wrong alignment 003A45E8
=== w7u_el (32 bit report) ===
kernel32: loader.c:2297: Test failed: 0: wrong alignment 00314688
=== w7pro64 (64 bit report) ===
kernel32: loader.c:2297: Test failed: 0: wrong alignment 00000000003C05D0
=== debian11b (64 bit WoW report) ===
mf: mf.c:6536: Test failed: Test 3: Unexpected hr 0xc00d36b2.
user32: input.c:4306: Test succeeded inside todo block: button_down_hwnd_todo 1: got MSG_TEST_WIN hwnd 00000000036E00E8, msg WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032