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=143395
Your paranoid android.
=== debian11 (32 bit report) ===
qwave: qos.c:86: Test succeeded inside todo block: Expected 0xdeadbeef, got -559038737
=== debian11 (32 bit ar:MA report) ===
qwave: qos.c:86: Test succeeded inside todo block: Expected 0xdeadbeef, got -559038737
=== debian11 (32 bit de report) ===
qwave: qos.c:86: Test succeeded inside todo block: Expected 0xdeadbeef, got -559038737
=== debian11 (32 bit fr report) ===
qwave: qos.c:86: Test succeeded inside todo block: Expected 0xdeadbeef, got -559038737
=== debian11 (32 bit he:IL report) ===
qwave: qos.c:86: Test succeeded inside todo block: Expected 0xdeadbeef, got -559038737
=== debian11 (32 bit hi:IN report) ===
qwave: qos.c:86: Test succeeded inside todo block: Expected 0xdeadbeef, got -559038737
=== debian11 (32 bit ja:JP report) ===
qwave: qos.c:86: Test succeeded inside todo block: Expected 0xdeadbeef, got -559038737
=== debian11 (32 bit zh:CN report) ===
qwave: qos.c:86: Test succeeded inside todo block: Expected 0xdeadbeef, got -559038737
=== debian11b (32 bit WoW report) ===
qwave: qos.c:86: Test succeeded inside todo block: Expected 0xdeadbeef, got -559038737
=== debian11b (64 bit WoW report) ===
qwave: qos.c:86: Test succeeded inside todo block: Expected 0xdeadbeef, got -559038737