https://bugs.winehq.org/show_bug.cgi?id=53273
Bug ID: 53273 Summary: user32:msg - test_PeekMessage2() sometimes fails on Windows 10 1709+ 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
user32:msg - test_PeekMessage2() sometimes fails on Windows 10 1709+:
msg.c:12835: 1st move event: 0200 1292b3 99 100 msg.c:12855: 2nd move event: 0200 1292b3 99 100 msg.c:12861: Test failed: message time not advanced: 1292b3 1292b3 msg.c:12862: Test failed: coords not changed: (99 100) (99 100) msg.c:12873: 3rd move event: 0200 1292b3 99 100 msg.c:12879: Test failed: message time not advanced: 1292b3 1292b3 msg.c:12880: Test failed: coords not changed: (99 100) (99 100)
https://test.winehq.org/data/patterns.html#user32:msg
https://bugs.winehq.org/show_bug.cgi?id=53273
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase
https://bugs.winehq.org/show_bug.cgi?id=53273
--- Comment #1 from François Gouget fgouget@codeweavers.com --- The two failures below happened once on 2022-08-02 on w10pro64-pt-BR-64 and may be related:
msg.c:12835: 1st move event: 0200 1212a5 99 100 msg.c:12855: 2nd move event: 0200 121322 104 105 msg.c:12873: 3rd move event: 0200 121380 109 110 msg.c:12921: Test failed: msg.message = 30 instead of WM_TIMER msg.c:12925: Test failed: msg.message = 30 instead of WM_TIMER
Where 30 == WM_TIMECHANGE.
https://bugs.winehq.org/show_bug.cgi?id=53273
--- Comment #2 from François Gouget fgouget@codeweavers.com --- There are more possible values for the unchanged coordinates. For instance: msg.c:13239: Test failed: coords not changed: (101 101) (101 101)
-
WineHQ Bugzilla