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=56909
Your paranoid android.
=== debian10 (32 bit report) ===
kernel32: console.c:2733: Test failed: got 16, expected 0 console.c:2923: Test succeeded inside todo block: got 0, expected 0 console.c:2934: Test succeeded inside todo block: got 0, expected 0 process.c:1628: Test failed: Console:winRight expected 79, but got 12
=== debian10 (32 bit Chinese:China report) ===
kernel32: console.c:2733: Test failed: got 16, expected 0 console.c:2923: Test succeeded inside todo block: got 0, expected 0 console.c:2934: Test succeeded inside todo block: got 0, expected 0 process.c:1628: Test failed: Console:winRight expected 79, but got 12
=== debian10 (32 bit WoW report) ===
kernel32: console.c:2733: Test failed: got 16, expected 0 console.c:2923: Test succeeded inside todo block: got 0, expected 0 console.c:2934: Test succeeded inside todo block: got 0, expected 0 process.c:1628: Test failed: Console:winRight expected 79, but got 12
=== debian10 (64 bit WoW report) ===
kernel32: console.c:2733: Test failed: got 16, expected 0 console.c:2923: Test succeeded inside todo block: got 0, expected 0 console.c:2934: Test succeeded inside todo block: got 0, expected 0 debugger.c:320: Test failed: GetThreadContext failed: 5 process.c:1628: Test failed: Console:winRight expected 79, but got 12