New subject: [Bug 54128] user32:msg - test_PeekMessage3() sometimes gets an unexpected WM_TIMECHANGE message on Windows 10

11 Dec 2022


      https://bugs.winehq.org/show_bug.cgi?id=54128
Bug ID: 54128
           Summary: user32:msg - test_PeekMessage3() sometimes gets an
                    unexpected WM_TIMECHANGE message on Windows 10
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: user32
          Assignee: wine-bugs@winehq.org
          Reporter: fgouget@codeweavers.com
test_PeekMessage3() sometimes gets an unexpected WM_TIMECHANGE message on
Windows 10:
msg.c:13549: Test failed: msg.message = 30 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 1
See https://test.winehq.org/data/patterns.html#user32:msg
Where
30 == WM_TIMECHANGE
275 == WM_TIMER
1024 == WM_USER
1025 == WM_USER + 1
This is similar to the issue happening in test_PeekMessage2() in bug 53273.
This last happened on 2022-12-09 on w10pro64-pt-BR where the Internet time
synchronization has not been disabled. So that may be the source of the
WM_TIMECHANGE messages.
The TestBot now has code to disable Internet time synchronization but the
snapshots have not all been updated. So this bug should be revisited once they
have been updated to see if the failures are still happening.
-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.

[Bug 54128] New: user32:msg - test_PeekMessage3() sometimes gets an unexpected WM_TIMECHANGE message on Windows 10