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 full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=124657
Your paranoid android.
=== debian11 (32 bit report) ===
advapi32: registry.c:1668: Test failed: expected ERROR_SUCCESS, got 2 registry.c:1670: Test failed: output is not what expected
=== debian11 (32 bit ar:MA report) ===
advapi32: registry.c:1668: Test failed: expected ERROR_SUCCESS, got 2 registry.c:1670: Test failed: output is not what expected
=== debian11 (32 bit de report) ===
advapi32: registry.c:1668: Test failed: expected ERROR_SUCCESS, got 2 registry.c:1670: Test failed: output is not what expected
=== debian11 (32 bit fr report) ===
advapi32: registry.c:1668: Test failed: expected ERROR_SUCCESS, got 2 registry.c:1670: Test failed: output is not what expected
=== debian11 (32 bit he:IL report) ===
advapi32: registry.c:1668: Test failed: expected ERROR_SUCCESS, got 2 registry.c:1670: Test failed: output is not what expected
=== debian11 (32 bit hi:IN report) ===
advapi32: registry.c:1668: Test failed: expected ERROR_SUCCESS, got 2 registry.c:1670: Test failed: output is not what expected
=== debian11 (32 bit ja:JP report) ===
advapi32: registry.c:1668: Test failed: expected ERROR_SUCCESS, got 2 registry.c:1670: Test failed: output is not what expected
=== debian11 (32 bit zh:CN report) ===
advapi32: registry.c:1668: Test failed: expected ERROR_SUCCESS, got 2 registry.c:1670: Test failed: output is not what expected
=== debian11 (32 bit WoW report) ===
advapi32: registry.c:1668: Test failed: expected ERROR_SUCCESS, got 2 registry.c:1670: Test failed: output is not what expected
=== debian11 (64 bit WoW report) ===
advapi32: registry.c:1668: Test failed: expected ERROR_SUCCESS, got 2 registry.c:1670: Test failed: output is not what expected