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=143736
Your paranoid android.
=== debian11 (32 bit report) ===
mfplat: mfplat.c:3615: Test succeeded inside todo block: Unexpected refcount 0.
=== debian11 (32 bit ar:MA report) ===
mfplat: mfplat.c:3615: Test succeeded inside todo block: Unexpected refcount 0.
=== debian11 (32 bit de report) ===
mfplat: mfplat.c:3615: Test succeeded inside todo block: Unexpected refcount 0.
=== debian11 (32 bit fr report) ===
mfplat: mfplat.c:3615: Test succeeded inside todo block: Unexpected refcount 0.
=== debian11 (32 bit he:IL report) ===
mfplat: mfplat.c:3615: Test succeeded inside todo block: Unexpected refcount 0.
=== debian11 (32 bit hi:IN report) ===
mfplat: mfplat.c:3615: Test succeeded inside todo block: Unexpected refcount 0.
=== debian11 (32 bit ja:JP report) ===
mfplat: mfplat.c:3615: Test succeeded inside todo block: Unexpected refcount 0.
=== debian11 (32 bit zh:CN report) ===
mfplat: mfplat.c:3615: Test succeeded inside todo block: Unexpected refcount 0.
=== debian11b (32 bit WoW report) ===
mfplat: mfplat.c:3615: Test succeeded inside todo block: Unexpected refcount 0.
=== debian11b (64 bit WoW report) ===
mfplat: mfplat.c:3615: Test succeeded inside todo block: Unexpected refcount 0.