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=134591
Your paranoid android.
=== debian11 (32 bit report) ===
ws2_32: sock.c:13852: Test failed: Incorrect error: 0 sock.c:13854: Test failed: Could not bind Unix socket: 10022
=== debian11 (32 bit ar:MA report) ===
ws2_32: sock.c:13852: Test failed: Incorrect error: 0 sock.c:13854: Test failed: Could not bind Unix socket: 10022
=== debian11 (32 bit de report) ===
ws2_32: sock.c:13852: Test failed: Incorrect error: 0 sock.c:13854: Test failed: Could not bind Unix socket: 10022
=== debian11 (32 bit fr report) ===
ws2_32: sock.c:13852: Test failed: Incorrect error: 0 sock.c:13854: Test failed: Could not bind Unix socket: 10022
=== debian11 (32 bit he:IL report) ===
ws2_32: sock.c:13852: Test failed: Incorrect error: 0 sock.c:13854: Test failed: Could not bind Unix socket: 10022
=== debian11 (32 bit hi:IN report) ===
ws2_32: sock.c:13852: Test failed: Incorrect error: 0 sock.c:13854: Test failed: Could not bind Unix socket: 10022
=== debian11 (32 bit ja:JP report) ===
ws2_32: sock.c:13852: Test failed: Incorrect error: 0 sock.c:13854: Test failed: Could not bind Unix socket: 10022
=== debian11 (32 bit zh:CN report) ===
ws2_32: sock.c:13852: Test failed: Incorrect error: 0 sock.c:13854: Test failed: Could not bind Unix socket: 10022
=== debian11b (32 bit WoW report) ===
ws2_32: sock.c:13852: Test failed: Incorrect error: 0 sock.c:13854: Test failed: Could not bind Unix socket: 10022
=== debian11b (64 bit WoW report) ===
ws2_32: sock.c:13852: Test failed: Incorrect error: 0 sock.c:13854: Test failed: Could not bind Unix socket: 10022