[PATCH 5/5] user32/tests: Fix existing winevents in test_DestroyWindow() 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=98466

Your paranoid android.


=== w10pro64 (32 bit report) ===

user32:
msg.c:9135: Test failed: MsgWaitForMultipleObjects failed 102
msg.c:9139: Test failed: WaitForSingleObject failed 102
msg.c:9143: Test failed: WaitForSingleObject failed ffffffff
msg.c:9149: Test failed: destroy child on thread exit: 0: the msg sequence is not complete: expected 0082 - actual 0000
msg.c:8955: Test failed: Failed to create child window
msg.c:8991: Test failed: WaitForSingleObject failed ffffffff

=== w1064_tsign (64 bit report) ===

user32:
msg.c:12737: Test failed: message time not advanced: 162eb 162eb
msg.c:12738: Test failed: coords not changed: (101 101) (101 101)
msg.c:12755: Test failed: message time not advanced: 162eb 162eb
msg.c:12756: Test failed: coords not changed: (101 101) (101 101)

=== w10pro64_zh_CN (64 bit report) ===

user32:
msg.c:12755: Test failed: message time not advanced: ef9f ef9f
msg.c:12756: Test failed: coords not changed: (105 105) (105 105)