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=124680
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
kernel32: debugger.c:1027: Test failed: ole32.dll was not reported
=== w7u_adm (32 bit report) ===
kernel32: debugger.c:1027: Test failed: ole32.dll was not reported debugger.c:2147: Test marked flaky: NtSetInformationDebugObject failed c0000008
=== w7u_el (32 bit report) ===
kernel32: debugger.c:1027: Test failed: ole32.dll was not reported debugger.c:2147: Test marked flaky: NtSetInformationDebugObject failed c0000008
=== w10pro64 (32 bit report) ===
kernel32: debugger.c:447: Test failed: unexpected thread debugger.c:450: Test failed: dwDebugEventCode = 2 debugger.c:451: Test failed: ExceptionCode = 584 debugger.c:453: Test failed: ExceptionAddress != DbgBreakPoint debugger.c:466: Test failed: dwDebugEventCode = 1
=== w10pro64_ar (64 bit report) ===
kernel32: debugger.c:1761: Test marked flaky: unexpected instruction pointer 00007FFC5224CE54
Report validation errors: kernel32:debugger returned success despite having failures