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=51131
Your paranoid android.
=== debian9 (32 bit report) ===
user32: msg.c:8713: Test failed: WaitForSingleObject failed 102 msg.c:8719: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead msg.c:8719: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead msg.c:8719: Test failed: destroy child on thread exit: 2: the msg sequence is not complete: expected 0014 - actual 0000
=== debian9 (64 bit WoW report) ===
user32: win.c:10127: Test failed: Expected foreground window 0, got 0000000000D20050 win.c:10133: Test failed: Expected foreground window 00000000000E0120, got 0000000000D20050 win.c:10169: Test failed: Expected foreground window 00000000000E0120, got 0000000000D20050 win.c:10171: Test failed: GetActiveWindow() = 0000000000000000 win.c:10171: Test failed: GetFocus() = 0000000000000000 win.c:10172: Test failed: Received WM_ACTIVATEAPP(1), did not expect it.