[PATCH 2/4] user32/tests: Fix existing winevents in test_messages() message sequences.

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

Your paranoid android.


=== w7u_2qxl (32 bit report) ===

user32:
msg.c:12690: Test failed: msg.message = 30 instead of WM_TIMER
msg.c:12694: Test failed: msg.message = 30 instead of WM_TIMER

=== w864 (32 bit report) ===

user32:
msg.c:13826: Test failed: 46: ShowWindow(SW_RESTORE): 8: the msg 0x8005 was expected, but got msg 0x0047 instead
msg.c:13826: Test failed: 46: ShowWindow(SW_RESTORE): 9: the msg 0x0047 was expected, but got msg 0x0009 instead
msg.c:13826: Test failed: 46: ShowWindow(SW_RESTORE): 10: the msg 0x0003 was expected, but got msg 0x8005 instead
msg.c:13826: Test failed: 46: ShowWindow(SW_RESTORE): 11: the msg 0x0005 was expected, but got msg 0x0047 instead
msg.c:13826: Test failed: 46: ShowWindow(SW_RESTORE): 13: the msg 0x800b was expected, but got msg 0x0003 instead
msg.c:13826: Test failed: 46: ShowWindow(SW_RESTORE): 15: the msg 0x0017 was expected, but got msg 0x0005 instead
msg.c:13826: Test failed: 46: ShowWindow(SW_RESTORE): 16: the msg sequence is not complete: expected 0000 - actual 800b