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=122895
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w7u_el (32 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w8 (32 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w864 (32 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w1064v1507 (32 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w1064v1809 (32 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w1064 (32 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w1064_tsign (32 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w10pro64 (32 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w864 (64 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w1064v1507 (64 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w1064v1809 (64 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w1064 (64 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w1064_2qxl (64 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w1064_tsign (64 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w10pro64 (64 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w10pro64_en_AE_u8 (64 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w10pro64_ar (64 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w10pro64_ja (64 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== w10pro64_zh_CN (64 bit report) ===
advapi32: registry.c:1670: Test failed: output is not what expected
=== debian11 (32 bit report) ===
advapi32: registry.c:1670: Test succeeded inside todo block: output is not what expected
=== debian11 (32 bit Arabic:Morocco report) ===
advapi32: registry.c:1670: Test succeeded inside todo block: output is not what expected
=== debian11 (32 bit German report) ===
advapi32: registry.c:1670: Test succeeded inside todo block: output is not what expected
=== debian11 (32 bit French report) ===
advapi32: registry.c:1670: Test succeeded inside todo block: output is not what expected
=== debian11 (32 bit Hebrew:Israel report) ===
advapi32: registry.c:1670: Test succeeded inside todo block: output is not what expected
=== debian11 (32 bit Hindi:India report) ===
advapi32: registry.c:1670: Test succeeded inside todo block: output is not what expected
=== debian11 (32 bit Japanese:Japan report) ===
advapi32: registry.c:1670: Test succeeded inside todo block: output is not what expected
=== debian11 (32 bit Chinese:China report) ===
advapi32: registry.c:1670: Test succeeded inside todo block: output is not what expected
=== debian11 (32 bit WoW report) ===
advapi32: registry.c:1670: Test succeeded inside todo block: output is not what expected
=== debian11 (64 bit WoW report) ===
advapi32: registry.c:1670: Test succeeded inside todo block: output is not what expected