[PATCH 4/5] user32/tests: Check for window class registration failure normally.

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

Your paranoid android.


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

user32:
win.c:2688: Test failed: style 0x200000: expected !100
win.c:2688: Test failed: style 0x300000: expected !100

=== w864 (64 bit report) ===

user32:
win.c:2688: Test failed: style 0x200000: expected !100
win.c:2688: Test failed: style 0x300000: expected !100

=== w10pro64_ja (64 bit report) ===

user32:
win.c:4373: Test failed: message 0100 available
win.c:4374: Test failed: hwnd 0000000000000000 message 0100
win.c:4403: Test failed: no message available
win.c:4404: Test failed: hwnd 0000000000000000 message 0100
win.c:10788: Test failed: pos = 00fa00fa
win.c:10792: Test failed: pos = 00fa00fa
win.c:10796: Test failed: pos = 00fa00fa

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

user32:
win.c:189: Test failed: didn't get start_event
win.c:4373: Test failed: message 0100 available
win.c:4374: Test failed: hwnd 0000000000000000 message 0100
win.c:4403: Test failed: no message available
win.c:4404: Test failed: hwnd 0000000000000000 message 0100
win.c:10788: Test failed: pos = 00fa00fa
win.c:10792: Test failed: pos = 00fa00fa
win.c:10796: Test failed: pos = 00fa00fa