[Bug 53210] New: user32:msg - test_dbcs_wm_char() sometimes gets a timing failure in Wine

[WineHQ Bugzilla]

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

            Bug ID: 53210
           Summary: user32:msg - test_dbcs_wm_char() sometimes gets a
                    timing failure in Wine
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: user32
          Assignee: wine-bugs(a)winehq.org
          Reporter: fgouget(a)codeweavers.com
      Distribution: ---

user32:msg - test_dbcs_wm_char() sometimes gets a timing failure in Wine:

msg.c:15198: Test failed: bad time 12b933de

https://test.winehq.org/data/patterns.html#user32:msg

This failure only appears to happen together with test_dbcs_wm_char()'s
Japanese and Chinese failures (see bug 52877) but it's much less frequent:
there are only 3 known instances (2022-05-18, 06-06 and 06-17).

Also, because it's a timing issue, it's not immediately clear how it is tied to
the locale.

-- 
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 53210] user32:msg - test_dbcs_wm_char() sometimes gets a timing failure in Wine

[WineHQ Bugzilla]

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

François Gouget <fgouget(a)codeweavers.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |source, testcase

-- 
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 53210] user32:msg - test_dbcs_wm_char() sometimes gets a timing failure in Wine

[WineHQ Bugzilla]

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

--- Comment #1 from Esme Povirk <madewokherd(a)gmail.com> ---
I'm a little confused by this check. It seems to specifically tolerate
timestamps up to 100 ticks in the future. Why can a timestamp be in the future,
and why is the acceptable limit 100 ticks?

-- 
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 53210] user32:msg - test_dbcs_wm_char() sometimes gets a timing failure in Wine

[WineHQ Bugzilla]

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

François Gouget <fgouget(a)codeweavers.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |julliard(a)winehq.org

-- 
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.