[PATCH v3 2/6] user32/tests: Add missing winevents to test_showwindow() message sequences.

[Connor McAdams]

On Thu, Sep 16, 2021 at 01:47:38PM -0500, Marvin wrote:
> 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=98166
> 
> Your paranoid android.
> 
> 
> === w8 (32 bit report) ===
> 
> user32:
> msg.c:13898: Test failed: 56: ShowWindow(SW_SHOWNOACTIVATE): 9: in msg 0x0047 expecting wParam 0x8170 got 0x1803
> msg.c:13898: Test failed: 56: ShowWindow(SW_SHOWNOACTIVATE): 10: the msg 0x0003 was expected, but got msg 0x0009 instead
> msg.c:13898: Test failed: 56: ShowWindow(SW_SHOWNOACTIVATE): 11: the msg 0x0005 was expected, but got msg 0x8005 instead
> msg.c:13898: Test failed: 56: ShowWindow(SW_SHOWNOACTIVATE): 15: in msg 0x0047 expecting wParam 0x1803 got 0x8160
> msg.c:13898: Test failed: 56: ShowWindow(SW_SHOWNOACTIVATE): 17: the msg 0x800b was expected, but got msg 0x0003 instead
> msg.c:13898: Test failed: 56: ShowWindow(SW_SHOWNOACTIVATE): 19: the msg 0x0017 was expected, but got msg 0x0005 instead
> msg.c:13898: Test failed: 56: ShowWindow(SW_SHOWNOACTIVATE): 20: the msg sequence is not complete: expected 0000 - actual 800b


These failures occurred in test_ShowWindow(), this patch effects
test_showwindow(), so these failures aren't caused by this patch. I'll
write a patch to fix these occasional failures and send it in the next
patch series.