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=147275
Your paranoid android.
=== w1064v1809 (32 bit report) ===
ucrtbase: string.c:831: Test failed: mbstowcs returned 18
=== w1064_tsign (32 bit report) ===
ucrtbase: string.c:831: Test failed: mbstowcs returned 18
=== w10pro64 (32 bit report) ===
ucrtbase: string.c:831: Test failed: mbstowcs returned 18
=== w10pro64_en_AE_u8 (32 bit report) ===
ucrtbase: string.c:831: Test failed: mbstowcs returned 18
=== w11pro64 (32 bit report) ===
ucrtbase: string.c:831: Test failed: mbstowcs returned 18
=== debian11 (32 bit report) ===
ucrtbase: string.c:831: Test failed: mbstowcs returned 18
=== debian11 (32 bit ar:MA report) ===
ucrtbase: string.c:831: Test failed: mbstowcs returned 18
=== debian11 (32 bit de report) ===
ucrtbase: string.c:831: Test failed: mbstowcs returned 18
=== debian11 (32 bit fr report) ===
ucrtbase: string.c:831: Test failed: mbstowcs returned 18
=== debian11 (32 bit he:IL report) ===
ucrtbase: string.c:831: Test failed: mbstowcs returned 18
=== debian11 (32 bit hi:IN report) ===
ucrtbase: string.c:831: Test failed: mbstowcs returned 18
=== debian11 (32 bit ja:JP report) ===
ucrtbase: string.c:831: Test failed: mbstowcs returned 18
=== debian11 (32 bit zh:CN report) ===
ucrtbase: string.c:831: Test failed: mbstowcs returned 18
=== debian11b (32 bit WoW report) ===
ucrtbase: string.c:831: Test failed: mbstowcs returned 18