[Bug 55495] New: ntdll:threadpool - test_tp_wait() sometimes gets an unexpected timeout in Wine

[WineHQ Bugzilla]

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

Bug ID: 55495
           Summary: ntdll:threadpool - test_tp_wait() sometimes gets an
                    unexpected timeout in Wine
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ntdll
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

ntdll:threadpool - test_tp_wait() sometimes gets an unexpected timeout in Wine:

threadpool.c:1715: Test failed: WaitForSingleObject returned 258
threadpool.c:1720: Test failed: expected info.userdata = 0, got 65536
threadpool.c:1729: Test failed: WaitForSingleObject returned 0

See See https://test.winehq.org/data/patterns.html#ntdll:threadpool

1715 & 1720: The timeout can also happen on Windows 8 and in that case the test
expects info.userdata to still be zero. But in Wine info.userdata still gets
set despite the timeout so the test fails. A hacky fix would be to expect the
correct behavior if (!broken(result == WAIT_TIMEOUT)) but it would be much
better to fix Wine's implementation.
Then the next WaitForSingleObject() does not time out which sounds a bit
similar to bug 55493.

The oldest known instance happened at the start of May and this seems to mostly
happen on the GitLab CI:
* 2023-07-28 MR!3441 (only the last two failures?)
* 2023-06-01 MR!2951 (only the last two failures?)
* 2023-05-31 fg-deb64-t32
* 2023-05-24 gitlab-debian-32
* 2023-05-02 MR!2734