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=135808
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
bcrypt: bcrypt.c:2661: Test failed: got 0 bcrypt.c:2673: Test failed: got 0 bcrypt.c:2679: Test failed: got 0xc000000d
=== w7u_adm (32 bit report) ===
bcrypt: bcrypt.c:2661: Test failed: got 0 bcrypt.c:2673: Test failed: got 0 bcrypt.c:2679: Test failed: got 0xc000000d
=== w7u_el (32 bit report) ===
bcrypt: bcrypt.c:2661: Test failed: got 0 bcrypt.c:2673: Test failed: got 0 bcrypt.c:2679: Test failed: got 0xc000000d
=== w8 (32 bit report) ===
bcrypt: bcrypt.c:2661: Test failed: got 0 bcrypt.c:2673: Test failed: got 0 bcrypt.c:2679: Test failed: got 0xc000000d
=== w8adm (32 bit report) ===
bcrypt: bcrypt.c:2661: Test failed: got 0 bcrypt.c:2673: Test failed: got 0 bcrypt.c:2679: Test failed: got 0xc000000d
=== w864 (32 bit report) ===
bcrypt: bcrypt.c:2661: Test failed: got 0 bcrypt.c:2673: Test failed: got 0 bcrypt.c:2679: Test failed: got 0xc000000d
=== w1064v1507 (32 bit report) ===
bcrypt: bcrypt.c:2661: Test failed: got 0 bcrypt.c:2673: Test failed: got 0 bcrypt.c:2679: Test failed: got 0xc000000d
=== w7pro64 (64 bit report) ===
bcrypt: bcrypt.c:2661: Test failed: got 0 bcrypt.c:2673: Test failed: got 0 bcrypt.c:2679: Test failed: got 0xc000000d
=== w864 (64 bit report) ===
bcrypt: bcrypt.c:2661: Test failed: got 0 bcrypt.c:2673: Test failed: got 0 bcrypt.c:2679: Test failed: got 0xc000000d
=== w1064v1507 (64 bit report) ===
bcrypt: bcrypt.c:2661: Test failed: got 0 bcrypt.c:2673: Test failed: got 0 bcrypt.c:2679: Test failed: got 0xc000000d
=== debian11 (32 bit report) ===
bcrypt: bcrypt.c:2554: Test succeeded inside todo block: got 13 bcrypt.c:2556: Test succeeded inside todo block: Decrypted output it's not what expected
=== debian11 (32 bit ar:MA report) ===
bcrypt: bcrypt.c:2554: Test succeeded inside todo block: got 13 bcrypt.c:2556: Test succeeded inside todo block: Decrypted output it's not what expected
=== debian11 (32 bit de report) ===
bcrypt: bcrypt.c:2554: Test succeeded inside todo block: got 13 bcrypt.c:2556: Test succeeded inside todo block: Decrypted output it's not what expected
=== debian11 (32 bit fr report) ===
bcrypt: bcrypt.c:2554: Test succeeded inside todo block: got 13 bcrypt.c:2556: Test succeeded inside todo block: Decrypted output it's not what expected
=== debian11 (32 bit he:IL report) ===
bcrypt: bcrypt.c:2554: Test succeeded inside todo block: got 13 bcrypt.c:2556: Test succeeded inside todo block: Decrypted output it's not what expected
=== debian11 (32 bit hi:IN report) ===
bcrypt: bcrypt.c:2554: Test succeeded inside todo block: got 13 bcrypt.c:2556: Test succeeded inside todo block: Decrypted output it's not what expected
=== debian11 (32 bit ja:JP report) ===
bcrypt: bcrypt.c:2554: Test succeeded inside todo block: got 13 bcrypt.c:2556: Test succeeded inside todo block: Decrypted output it's not what expected
=== debian11 (32 bit zh:CN report) ===
bcrypt: bcrypt.c:2554: Test succeeded inside todo block: got 13 bcrypt.c:2556: Test succeeded inside todo block: Decrypted output it's not what expected
=== debian11b (32 bit WoW report) ===
bcrypt: bcrypt.c:2554: Test succeeded inside todo block: got 13 bcrypt.c:2556: Test succeeded inside todo block: Decrypted output it's not what expected
=== debian11b (64 bit WoW report) ===
bcrypt: bcrypt.c:2554: Test succeeded inside todo block: got 13 bcrypt.c:2556: Test succeeded inside todo block: Decrypted output it's not what expected