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=138091
Your paranoid android.
=== w8 (32 bit report) ===
Report validation errors: msxml3:domdoc has no test summary line (early exit of the main process?) msxml3:domdoc has unaccounted for skip messages msxml3:domdoc returned a non-zero exit code despite reporting no failures
=== w8adm (32 bit report) ===
Report validation errors: msxml3:domdoc has no test summary line (early exit of the main process?) msxml3:domdoc has unaccounted for skip messages msxml3:domdoc returned a non-zero exit code despite reporting no failures
=== w864 (32 bit report) ===
Report validation errors: msxml3:domdoc has no test summary line (early exit of the main process?) msxml3:domdoc has unaccounted for skip messages msxml3:domdoc returned a non-zero exit code despite reporting no failures
=== debian11b (64 bit WoW report) ===
winhttp: notification.c:118: Test failed: 297: expected status 0x8 got 0x800 notification.c:118: Test failed: 297: expected status 0x8 got 0x800 winhttp.c:5740: Test failed: failed to send request 12002 winhttp.c:5759: Test failed: failed to send request 12002 winhttp.c:5764: Test succeeded inside todo block: unexpected success winhttp: Timeout