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=130803
Your paranoid android.
=== debian11 (32 bit report) ===
Report validation errors: kernel32:fiber has no test summary line (early exit of the main process?)
=== debian11 (32 bit ar:MA report) ===
Report validation errors: kernel32:fiber has no test summary line (early exit of the main process?)
=== debian11 (32 bit de report) ===
Report validation errors: kernel32:fiber has no test summary line (early exit of the main process?)
=== debian11 (32 bit fr report) ===
Report validation errors: kernel32:fiber has no test summary line (early exit of the main process?)
=== debian11 (32 bit he:IL report) ===
Report validation errors: kernel32:fiber has no test summary line (early exit of the main process?)
=== debian11 (32 bit hi:IN report) ===
Report validation errors: kernel32:fiber has no test summary line (early exit of the main process?)
=== debian11 (32 bit ja:JP report) ===
Report validation errors: kernel32:fiber has no test summary line (early exit of the main process?)
=== debian11 (32 bit zh:CN report) ===
Report validation errors: kernel32:fiber has no test summary line (early exit of the main process?)
=== debian11b (32 bit WoW report) ===
Report validation errors: kernel32:fiber has no test summary line (early exit of the main process?)
=== debian11b (64 bit WoW report) ===
Report validation errors: kernel32:fiber has no test summary line (early exit of the main process?)