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=130818
Your paranoid android.
=== debian11b (32 bit WoW report) ===
advapi32: registry.c:2837: Test succeeded inside todo block: RegOpenKeyExA failed: 0 registry.c:2842: Test succeeded inside todo block: RegOpenKeyExA failed: 0 registry.c:2861: Test succeeded inside todo block: 00000000: wrong value 64/64 registry.c:2863: Test succeeded inside todo block: 00000200: wrong value 64/64 registry.c:2868: Test succeeded inside todo block: 00000000: wrong value 0/0 registry.c:2869: Test succeeded inside todo block: 00000100: wrong value 0/0 registry.c:2870: Test succeeded inside todo block: 00000200: wrong value 0/0 registry.c:3168: Test succeeded inside todo block: RegOpenKeyExA failed: 0 registry.c:3174: Test succeeded inside todo block: RegOpenKeyExA failed: 0 registry.c:3180: Test succeeded inside todo block: RegOpenKeyExA failed: 0 registry.c:3206: Test succeeded inside todo block: found equals 1 registry.c:3208: Test succeeded inside todo block: found equals 1 registry.c:3210: Test succeeded inside todo block: found equals 1 registry.c:3212: Test succeeded inside todo block: found equals 0 registry.c:3214: Test succeeded inside todo block: wrong number of subkeys: 9 registry.c:3216: Test succeeded inside todo block: found equals 0 registry.c:3218: Test succeeded inside todo block: found equals 1 registry.c:3220: Test succeeded inside todo block: wrong number of subkeys: 9 registry.c:3222: Test succeeded inside todo block: found equals 1