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=46567
Your paranoid android.
=== wvistau64_zh_CN (32 bit report) ===
user32: dce.c:648: Test failed: wrong window
=== w2003std (32 bit report) ===
user32: dde: Timeout
=== w7pro64 (64 bit report) ===
user32: menu.c:794: Test failed: width of owner drawn menu item is wrong. Got 53 expected 24 menu.c:798: Test failed: Height of owner drawn menu item is wrong. Got 10 expected 19
=== w2003std (32 bit report) ===
user32: sysparams: Timeout
=== 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
=== debian9 (32 bit report) ===
user32: input.c:2566: Test failed: 200: wrong originId 1/2 input.c:2575: Test failed: 200: wrong originId 1/2 input.c:2566: Test failed: 200: wrong originId 1/2 input.c:2575: Test failed: 200: wrong originId 1/2
=== debian9 (32 bit WoW 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