Hi,
While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=39191
Your paranoid android.
=== wvistau64 (32 bit misc) === misc.c:803: Test failed: exit_event2 was not set (102) ucrtbase:misc has unaccounted for failure messages ucrtbase:misc returned success despite having failures
=== wvistau64_zh_CN (32 bit misc) === misc.c:803: Test failed: exit_event2 was not set (102) ucrtbase:misc has unaccounted for failure messages ucrtbase:misc returned success despite having failures
=== wvistau64_fr (32 bit misc) === misc.c:803: Test failed: exit_event2 was not set (102) ucrtbase:misc has unaccounted for failure messages ucrtbase:misc returned success despite having failures
=== wvistau64_he (32 bit misc) === misc.c:803: Test failed: exit_event2 was not set (102) ucrtbase:misc has unaccounted for failure messages ucrtbase:misc returned success despite having failures
=== w7u (32 bit misc) === misc.c:803: Test failed: exit_event2 was not set (102) ucrtbase:misc has unaccounted for failure messages ucrtbase:misc returned success despite having failures
=== w1064 (32 bit misc) === misc.c:803: Test failed: exit_event2 was not set (102) ucrtbase:misc has unaccounted for failure messages ucrtbase:misc returned success despite having failures
=== wvistau64 (64 bit misc) === misc.c:803: Test failed: exit_event2 was not set (102) ucrtbase:misc has unaccounted for failure messages ucrtbase:misc returned success despite having failures
=== w1064 (64 bit misc) === misc.c:803: Test failed: exit_event2 was not set (102) ucrtbase:misc has unaccounted for failure messages ucrtbase:misc returned success despite having failures