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=126900
Your paranoid android.
=== w1064v1507 (32 bit report) ===
winhttp: notification.c:118: Test failed: 332: expected status 0x10 got 0x1 notification.c:118: Test failed: 332: expected status 0x10 got 0x2 notification.c:118: Test failed: 332: expected status 0x10 got 0x4 notification.c:118: Test failed: 332: expected status 0x10 got 0x8
=== debian11 (32 bit report) ===
wldap32: parse.c:245: Test failed: ldap_get_next_page_s failed 0x51 parse.c:246: Test failed: expected res != NULL parse.c:247: Test failed: got 3735928559 Unhandled exception: page fault on read access to 0x0000001c in 32-bit code (0x6f8d7bce).