[PATCH] user32/tests: Fix some msg test failures.

[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=56422

Your paranoid android.


=== wvistau64_he (32 bit report) ===

user32:
msg.c:16172: Test failed: 4: WaitForSingleObject failed

=== w7u (32 bit report) ===

user32:
msg.c:13786: Test failed: CreateDialogParam_3: 14: the msg 0x001c was expected, but got msg 0x0083 instead

=== w8 (32 bit report) ===

user32:
msg.c:14593: Test failed: unexpected message 31f
msg.c:14594: Test failed: bad wparam 1
msg.c:14600: Test failed: unicode WM_CHAR: 0: the msg sequence is not complete: expected 0102 - actual 0000

=== w8adm (32 bit report) ===

user32:
msg.c:12837: Test failed: WmMouseHoverSeq: 3: the msg 0x0118 was expected, but got msg 0x001a instead
msg.c:12837: Test failed: WmMouseHoverSeq: 4: the msg 0x02a1 was expected, but got msg 0x001a instead
msg.c:12837: Test failed: WmMouseHoverSeq: 5: the msg sequence is not complete: expected 0000 - actual 0118

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

user32:
msg.c:9337: Test failed: Shift+MouseButton press/release: 7: the msg 0x0202 was expected, but got msg 0x0007 instead
msg.c:9337: Test failed: Shift+MouseButton press/release: 8: the msg 0x0202 was expected, but got msg 0x0101 instead
msg.c:9337: Test failed: Shift+MouseButton press/release: 10: the msg 0x0101 should have been sent
msg.c:9337: Test failed: Shift+MouseButton press/release: 11: the msg 0x0101 was expected, but got msg 0x0202 instead
msg.c:9337: Test failed: Shift+MouseButton press/release: 12: the msg sequence is not complete: expected 0000 - actual 0202
msg.c:10210: Test failed: did not get expected count for minimum timeout (54 != ~100).

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

user32:
msg.c:10280: Test failed: did not get expected count for minimum timeout (54 != ~100).

=== debian10 (32 bit report) ===

user32:
msg.c:5148: Test succeeded inside todo block: ShowWindow(SW_SHOWMINIMIZED):overlapped: marked "todo_wine" but succeeds

Report errors:
user32:msg prints too much data (35222 bytes)

=== debian10 (32 bit French report) ===

user32:
msg.c:5148: Test succeeded inside todo block: ShowWindow(SW_SHOWMINIMIZED):overlapped: marked "todo_wine" but succeeds

Report errors:
user32:msg prints too much data (35222 bytes)

=== debian10 (32 bit Japanese:Japan report) ===

user32:
msg.c:5148: Test succeeded inside todo block: ShowWindow(SW_SHOWMINIMIZED):overlapped: marked "todo_wine" but succeeds

Report errors:
user32:msg prints too much data (35222 bytes)

=== debian10 (32 bit Chinese:China report) ===

user32:
msg.c:5148: Test succeeded inside todo block: ShowWindow(SW_SHOWMINIMIZED):overlapped: marked "todo_wine" but succeeds

Report errors:
user32:msg prints too much data (35222 bytes)

=== debian10 (32 bit WoW report) ===

user32:
msg.c:5148: Test succeeded inside todo block: ShowWindow(SW_SHOWMINIMIZED):overlapped: marked "todo_wine" but succeeds

Report errors:
user32:msg prints too much data (35222 bytes)

=== debian10 (64 bit WoW report) ===

user32:
msg.c:5148: Test succeeded inside todo block: ShowWindow(SW_SHOWMINIMIZED):overlapped: marked "todo_wine" but succeeds

Report errors:
user32:msg prints too much data (35222 bytes)