[Bug 54026] New: user32:msg receives unexpected messages in the 49000+ range on w11pro64_nv

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=54026

Bug ID: 54026
           Summary: user32:msg receives unexpected messages in the 49000+
                    range on w11pro64_nv
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: user32
          Assignee: [e-mail]
          Reporter: [e-mail]

user32:msg receives unexpected messages in the 49000+ range on w11pro64_nv:

msg.c:13518: Test failed: msg.message = 49667 instead of WM_TIMER
or
msg.c:13499: Test failed: msg.message = 49815 instead of WM_TIMER
or
msg.c:13549: Test failed: msg.message = 49663 instead of WM_TIMER
msg.c:13552: Test failed: msg.message = 275 instead of WM_USER + 1
msg.c:13554: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:13564: Test failed: msg.message = 1025 instead of WM_TIMER
msg.c:13566: Test failed: msg.message = 275 instead of WM_USER
msg.c:13568: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:13577: Test failed: msg.message = 1024 instead of WM_TIMER
msg.c:13579: Test failed: expected PeekMessage to return FALSE, got 1or
or
msg.c:13518: Test failed: msg.message = 49650 instead of WM_TIMER
msg.c:13521: Test failed: msg.message = 275 instead of WM_USER
msg.c:13523: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:13534: Test failed: msg.message = 1024 instead of WM_TIMER
msg.c:13536: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:13546: Test failed: msg.message = 275 instead of WM_USER
msg.c:13549: Test failed: msg.message = 1024 instead of WM_TIMER
or
msg.c:13499: Test failed: msg.message = 49668 instead of WM_TIMER
msg.c:13503: Test failed: msg.message = 49668 instead of WM_TIMER

See http://winetest.dolphin/data/patterns.html#user32:msg

Where:
275 == WM_TIMER
1024 == WM_USER

These failures don't happen on other w11pro64 test configurations so it is
likely that these messages are generated by some part of the NVIDIA driver
despite it being installed without its GUI precisely to avoid this type of
issue. So it seems the test will have to accommodate these extra messages
despite their value changing from one run to the next.