[PATCH v2 6/6] user32/tests: Test changing activation from within WM_ACTIVATE's WA_INACTIVE message

[Marvin]

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=54841

Your paranoid android.


=== wvistau64_zh_CN (32 bit report) ===

Report errors:
user32:win is missing some failure messages

=== w1064v1809 (32 bit report) ===

user32:
win.c:3163: Test failed: SetActiveWindow returned 00000000 instead of 000803BE
win.c:3221: Test failed: expected 000803BE, got 00000000
win.c:3863: Test failed: hwnd 00040038 message 0060
win.c:4003: Test failed: hwnd 00BD0380/00BD0380 message 00a1
win.c:3307: Test failed: SetActiveWindow(0) returned 00000000 instead of 000803BE

=== w1064v1809 (64 bit report) ===

user32:
win.c:3163: Test failed: SetActiveWindow returned 0000000000000000 instead of 00000000000803BE
win.c:3221: Test failed: expected 00000000000803BE, got 0000000000000000
win.c:3863: Test failed: hwnd 0000000000040038 message 0060
win.c:4003: Test failed: hwnd 0000000000BD0380/0000000000BD0380 message 00a1
win.c:3307: Test failed: SetActiveWindow(0) returned 0000000000000000 instead of 00000000000803BE

=== debian9 (64 bit WoW report) ===

user32:
msg.c:8746: Test failed: WaitForSingleObject failed 102
msg.c:8752: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead
msg.c:8752: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead
msg.c:8752: Test failed: destroy child on thread exit: 2: the msg sequence is not complete: expected 0014 - actual 0000