Re: user32: Workaround SetForegroundWindow failure due to foreground lock timeout

[Marvin]

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://newtestbot.winehq.org/JobDetails.pl?Key=5923

Your paranoid android.


=== w8 (32 bit win) ===
win.c:6403: Test failed: 0x80/0x1c10000: window rect 0,0-1024,768 must be in 0,0-1024,728
win.c:6425: Test failed: 0x80/0x1010000: window rect 0,0-1024,768
win.c:6403: Test failed: 0x80/0x81c10000: window rect 0,0-1024,768 must be in 0,0-1024,728
win.c:6403: Test failed: 0/0x41c10000: window rect 0,0-1024,768 must be in 0,0-1024,728
win.c:6403: Test failed: 0x40000/0x41c10000: window rect 0,0-1024,768 must be in 0,0-1024,728
win.c:6403: Test failed: 0x80/0x41c10000: window rect 0,0-1024,768 must be in 0,0-1024,728
win.c:6403: Test failed: 0x80/0x1c50000: window rect 0,0-1024,768 must be in 0,0-1024,728
win.c:6425: Test failed: 0x80/0x1050000: window rect 0,0-1024,768
win.c:6403: Test failed: 0x80/0x1c10000: window rect 0,0-1024,768 must be in 0,0-1024,728
win.c:6425: Test failed: 0x80/0x1410000: window rect 0,0-1024,768
win.c:6186: Test failed: wrong error 31