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=77967
Your paranoid android.
=== w1064v1507 (32 bit report) ===
user32: win.c:9688: Test failed: Timed out waiting for the child process win.c:11139: Test failed: 0005015C: expected next 0006004E, got 00000000 win.c:11154: Test failed: 0004004C: expected next 00040044, got 00000000 win.c:11164: Test failed: 0004004C: expected next 00040044, got 00000000 win.c:11179: Test failed: 0004004C: expected next 00040044, got 00000000 win.c:11203: Test failed: 0004004C: expected next 00040044, got 00000000 win.c:11212: Test failed: 0004004C: expected next 00040044, got 00000000
=== w1064v1809 (32 bit report) ===
user32: win.c:781: Test failed: rects do not match (3,26)-(157,26) / (0,0)-(0,0)
=== w1064v1809_2scr (32 bit report) ===
user32: win.c:9688: Test failed: Timed out waiting for the child process
=== w1064v1809_ja (32 bit report) ===
user32: win.c:4059: Test failed: hwnd 00040062 message 7fff win.c:4138: Test failed: hwnd 00040062/008E0348 message 7fff win.c:4141: Test failed: hwnd 00040062/008E0348 message 7fff
=== w1064v1809_zh_CN (32 bit report) ===
user32: win.c:4059: Test failed: hwnd 0001038C message 0282 win.c:4138: Test failed: hwnd 0001038C/000B03DA message 0282 win.c:4141: Test failed: hwnd 0001038C/000B03DA message 0282
=== w1064v1809 (64 bit report) ===
user32: win.c:781: Test failed: rects do not match (3,26)-(157,26) / (0,0)-(0,0)