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=45071
Your paranoid android.
=== wvistau64 (32 bit report) ===
user32: dce.c:648: Test failed: wrong window
=== wvistau64_he (32 bit report) ===
user32: dce.c:127: Test failed: wrong window
=== w7u (32 bit report) ===
user32: dce.c:658: Test failed: DC for destroyed window not reused
=== w2003std (32 bit report) ===
user32: dde: Timeout
=== w8adm (32 bit report) ===
user32: msg.c:16463: Test failed: SetFocus on a child window: 4: the msg 0x001c was expected, but got msg 0x0047 instead
=== w2003std (32 bit report) ===
user32: sysparams: Timeout
=== wvistau64 (task log) ===
Task errors: TestBot process got stuck or died unexpectedly The previous 1 run(s) terminated abnormally
=== w8 (32 bit report) ===
user32: sysparams.c:2514: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out sysparams.c:2525: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1
=== w8adm (32 bit report) ===
user32: sysparams.c:2514: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out sysparams.c:2525: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1
=== w864 (32 bit report) ===
user32: sysparams.c:2514: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out sysparams.c:2525: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1
=== wvistau64 (task log) ===
Task errors: TestBot process got stuck or died unexpectedly The previous 1 run(s) terminated abnormally
=== wvistau64 (task log) ===
Task errors: TestBot process got stuck or died unexpectedly The previous 1 run(s) terminated abnormally
=== debian9 (32 bit French report) ===
user32: menu.c:2354: Test failed: test 27 menu: Timeout
=== debian9 (32 bit WoW report) ===
user32: msg.c:8405: Test failed: WaitForSingleObject failed 102 msg.c:8411: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead msg.c:8411: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead msg.c:8411: Test failed: destroy child on thread exit: 2: the msg sequence is not complete: expected 0014 - actual 0000