Hi,
While running your changed tests, 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=60747
Your paranoid android.
=== wxppro (32 bit report) ===
kernel32: locale.c:4903: Test failed: got 4 locale.c:4904: Test failed: got 333
=== w2003std (32 bit report) ===
kernel32: locale.c:4903: Test failed: got 4 locale.c:4904: Test failed: got 333
=== wvistau64 (32 bit report) ===
kernel32: locale.c:4903: Test failed: got 4 locale.c:4904: Test failed: got 333
=== w2008s64 (32 bit report) ===
kernel32: locale.c:4903: Test failed: got 4 locale.c:4904: Test failed: got 333
=== w7u (32 bit report) ===
kernel32: locale.c:4903: Test failed: got 4 locale.c:4904: Test failed: got 333
=== wvistau64 (64 bit report) ===
kernel32: locale.c:4903: Test failed: got 4 locale.c:4904: Test failed: got 333
=== w2008s64 (64 bit report) ===
kernel32: locale.c:4903: Test failed: got 4 locale.c:4904: Test failed: got 333
=== debian10 (32 bit report) ===
kernel32: debugger: Timeout
=== debian10 (32 bit Chinese:China report) ===
kernel32: comm.c:918: Test failed: OutQueue should not be empty debugger: Timeout
=== debian10 (32 bit WoW report) ===
kernel32: comm.c:918: Test failed: OutQueue should not be empty debugger.c:320: Test failed: GetThreadContext failed: 5 debugger.c:320: Test failed: GetThreadContext failed: 5
=== debian10 (64 bit WoW report) ===
kernel32: debugger: Timeout