https://bugs.winehq.org/show_bug.cgi?id=55204
Bug ID: 55204 Summary: ws2_32:sock - test_close_events() sometimes misses the close event on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs@winehq.org Reporter: fgouget@codeweavers.com
ws2_32:sock - test_close_events() sometimes misses the close event on Windows:
sock.c:6845: Test failed: got events 0 sock.c:6858: Test failed: got -1 sock.c:6872: Test failed: got events 0 sock.c:6890: Test failed: expected timeout
See https://test.winehq.org/data/patterns.html#ws2_32:sock
This happened 9 times in the past 8 months, mostly on Windows 7 but it did happen once on Windows 10: * 2022-12-14 win7_newtb-w7u-adm * 2023-02-08 win22H2_fgtb-w10pro64-64 * 2023-02-22 win7_newtb-w7u-de * 2023-03-17 win7_newtb-w7u-de * 2023-03-27 win7_newtb-w7u-2qxl * 2023-03-27 win7_newtb-w7u * 2023-05-04 win7_newtb-w7u * 2023-05-10 win7_newtb-w7u-es * 2023-06-29 win7_newtb-w7u
There are also two cases where the second events check does get an FD_CLOSE event:
sock.c:6697: Test failed: got events 0 sock.c:6710: Test failed: got -1 sock.c:6712: Test failed: expected timeout sock.c:6712: Test failed: got events 0x20
* 2022-11-28 win21H1_newtb-w10pro64-he-64 * 2023-02-27 win22H2_fgtb-w10pro64-rx550-64
https://bugs.winehq.org/show_bug.cgi?id=55204
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase
https://bugs.winehq.org/show_bug.cgi?id=55204
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #1 from Zeb Figura z.figura12@gmail.com --- This is getting kind of ridiculous; how much time does Windows need to send FIN over a loopback connection?