https://bugs.winehq.org/show_bug.cgi?id=53239
Bug ID: 53239 Summary: dpnet:client - test_enum_hosts() and test_enum_hosts_peer() fail randomly on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-dplay Assignee: wine-bugs@winehq.org Reporter: fgouget@codeweavers.com
dpnet:client - test_enum_hosts() and test_enum_hosts_peer() fail randomly on Windows:
client.c:323: Test failed: got 0x80004005 or client.c:753: Test failed: got 0x80004005
https://test.winehq.org/data/patterns.html#dpnet:client
In both cases the API that fails is IDirectPlay8Client_CancelAsyncOperation() so this looks like a race condition.
The failure rate (~4.4%) is low enough to cause false positives. Strangely enough all but one of the failures happened on w7u, w7pro64 and w10pro64 (21H1). That means none of the failures happened on Windows 10 1507 to 2009!
https://bugs.winehq.org/show_bug.cgi?id=53239
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase
https://bugs.winehq.org/show_bug.cgi?id=53239
--- Comment #1 from François Gouget fgouget@codeweavers.com --- This can also result in an invalid lastAsyncHandle (or async2?) value:
client.c:324: Test failed: got 0x00000003 or client.c:754: Test failed: got 0x00000003
The trace is actually strange: clearly it's lastAsyncHandle which is being tested but the ok() test uses async2 for the 'got' value:
todo_wine ok(lastAsyncHandle == async2, "got 0x%08lx\n", async2);
https://bugs.winehq.org/show_bug.cgi?id=53239
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|dpnet:client - |dpnet:client - |test_enum_hosts() and |test_enum_hosts() and |test_enum_hosts_peer() fail |test_enum_hosts_peer() fail |randomly on Windows |randomly on Windows (flaky)
--- Comment #2 from François Gouget fgouget@codeweavers.com --- This issue is still present but is marked flaky so it does not appear on the failure patterns anymore.