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=125058
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
msvcrt: 0384:string: unhandled exception c0000005 at 77CB58D1
=== w7u_adm (32 bit report) ===
msvcrt: 0860:string: unhandled exception c0000005 at 761458D1
=== w7u_el (32 bit report) ===
msvcrt: 0860:string: unhandled exception c0000005 at 76CA58D1
=== w8 (32 bit report) ===
msvcrt: 0ab8:string: unhandled exception c0000005 at 76ED26BE
=== w8adm (32 bit report) ===
msvcrt: 0320:string: unhandled exception c0000005 at 76DC26BE
=== w864 (32 bit report) ===
msvcrt: 0be0:string: unhandled exception c0000005 at 772E26BE
=== w1064v1507 (32 bit report) ===
msvcrt: 0f8c:string: unhandled exception c0000005 at 74BF4E0E
=== w1064v1809 (32 bit report) ===
msvcrt: 1c74:string: unhandled exception c0000005 at 76005BBD
=== w1064 (32 bit report) ===
msvcrt: 1654:string: unhandled exception c0000005 at 768049DB
=== w1064_tsign (32 bit report) ===
msvcrt: 0b2c:string: unhandled exception c0000005 at 763449DB
=== w10pro64 (32 bit report) ===
msvcrt: 1eb8:string: unhandled exception c0000005 at 777C49DB
=== w864 (64 bit report) ===
msvcrt: 0bb4:string: unhandled exception c0000005 at 00007FFDCD7117B5
=== w1064v1507 (64 bit report) ===
msvcrt: 0168:string: unhandled exception c0000005 at 00007FFFDF4B7ACC
=== w1064v1809 (64 bit report) ===
msvcrt: 1d38:string: unhandled exception c0000005 at 00007FFAD15E7C89
=== w1064 (64 bit report) ===
msvcrt: 1d48:string: unhandled exception c0000005 at 00007FFEE39D7C19
=== w1064_2qxl (64 bit report) ===
msvcrt: 1d34:string: unhandled exception c0000005 at 00007FF8F52F7C19
=== w1064_adm (64 bit report) ===
msvcrt: 1a84:string: unhandled exception c0000005 at 00007FFAE7097C19
=== w1064_tsign (64 bit report) ===
msvcrt: 1ed0:string: unhandled exception c0000005 at 00007FFD842B7C19
=== w10pro64 (64 bit report) ===
msvcrt: 1d74:string: unhandled exception c0000005 at 00007FFCF1417C19
=== w10pro64_en_AE_u8 (64 bit report) ===
msvcrt: 1a64:string: unhandled exception c0000005 at 00007FF99DCF7C19
=== w10pro64_ar (64 bit report) ===
msvcrt: 071c:string: unhandled exception c0000005 at 00007FFC518C7C19
=== w10pro64_ja (64 bit report) ===
msvcrt: 0f74:string: unhandled exception c0000005 at 00007FFA413E7C19
=== w10pro64_zh_CN (64 bit report) ===
msvcrt: 2034:string: unhandled exception c0000005 at 00007FFD3B617C19
=== debian11 (32 bit report) ===
msvcrt: string.c:2847: Test failed: Skipping _mbsupr_s_l tests Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x6a2ba670).
=== debian11 (32 bit ar:MA report) ===
msvcrt: string.c:2847: Test failed: Skipping _mbsupr_s_l tests Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x6a2ba670).
=== debian11 (32 bit de report) ===
msvcrt: string.c:2847: Test failed: Skipping _mbsupr_s_l tests Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x6a2ba670).
=== debian11 (32 bit fr report) ===
msvcrt: string.c:2847: Test failed: Skipping _mbsupr_s_l tests Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x6a2ba670).
=== debian11 (32 bit he:IL report) ===
msvcrt: string.c:2847: Test failed: Skipping _mbsupr_s_l tests Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x6a2ba670).
=== debian11 (32 bit hi:IN report) ===
msvcrt: string.c:2847: Test failed: Skipping _mbsupr_s_l tests Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x6a2ba670).
=== debian11 (32 bit ja:JP report) ===
msvcrt: string.c:2847: Test failed: Skipping _mbsupr_s_l tests Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x6a2ba670).
=== debian11 (32 bit zh:CN report) ===
msvcrt: string.c:2847: Test failed: Skipping _mbsupr_s_l tests Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x6a2ba670).
=== debian11 (build log) ===
Use of uninitialized value $Flaky in addition (+) at /home/testbot/lib/WineTestBot/LogUtils.pm line 720, <$LogFile> line 24882. Use of uninitialized value $Flaky in addition (+) at /home/testbot/lib/WineTestBot/LogUtils.pm line 720, <$LogFile> line 24882. Use of uninitialized value $Flaky in addition (+) at /home/testbot/lib/WineTestBot/LogUtils.pm line 720, <$LogFile> line 24882.
=== debian11 (32 bit WoW report) ===
msvcrt: string.c:2847: Test failed: Skipping _mbsupr_s_l tests Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x6a2ba670).
=== debian11 (64 bit WoW report) ===
msvcrt: string.c:2847: Test failed: Skipping _mbsupr_s_l tests Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x0000006a0b9ec4).