[Bug 31927] New: ws2_32: sock.c fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0' - wine-bugs

List overview All Threads

newer

[Bug 31927] New: ws2_32: sock.c fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0'

older

[Bug 53099] New: wineserver (gcc...

[Bug 54094] New: kernel32:process...

wine-bugs＠winehq.org

9 Oct 2012 9 Oct '12

6:42 p.m.

http://bugs.winehq.org/show_bug.cgi?id=31927

Bug #: 31927 Summary: ws2_32: sock.c fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0' Product: Wine Version: 1.5.14 Platform: x86 OS/Version: Linux Status: NEW Keywords: download, testcase Severity: minor Priority: P2 Component: winsock AssignedTo: wine-bugs@winehq.org ReportedBy: austinenglish@gmail.com Classification: Unclassified

Running in a loop for about 15 minutes, I got: sock.c:5385: Test succeeded inside todo block: GetQueuedCompletionStatus returned 0 sock.c:5386: Test succeeded inside todo block: Last error was 64 make: *** [sock.ok] Error 2

-- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

Show replies by date

wine-bugs＠winehq.org

11 Oct 11 Oct

4:01 p.m.

New subject: [Bug 31927] ws2_32: sock.c fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0'

http://bugs.winehq.org/show_bug.cgi?id=31927

Erich Hoover ehoover@mines.edu changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |ehoover@mines.edu

wine-bugs＠winehq.org

13 Jun 13 Jun

7:41 p.m.

New subject: [Bug 31927] ws2_32: sock.c fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0'

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

--- Comment #1 from Ken Sharp imwellcushtymelike@gmail.com --- Is this still an issue in Wine 1.7.45 or later?

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

wine-bugs＠winehq.org

7:42 p.m.

New subject: [Bug 31927] ws2_32: sock.c fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0'

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

Ken Sharp imwellcushtymelike@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source

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

wine-bugs＠winehq.org

4 Jul 4 Jul

6:22 a.m.

New subject: [Bug 31927] ws2_32: sock.c fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0'

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

--- Comment #2 from Austin English austinenglish@gmail.com --- Running in a loop, after about 6 minutes I got: ../../../tools/runtest -q -P wine -T ../../.. -M ws2_32.dll -p ws2_32_test.exe.so sock && touch sock.ok fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} fixme:winsock:convert_socktype_w2u unhandled Windows socket type 0 fixme:winsock:WS_EnterSingleProtocolW unknown Protocol <0xffffffff> fixme:winsock:convert_socktype_w2u unhandled Windows socket type 0 fixme:winsock:WS_EnterSingleProtocolW unknown Protocol <0x0000dead> fixme:winsock:convert_socktype_w2u unhandled Windows socket type 0 fixme:winsock:convert_proto_w2u unhandled Windows socket protocol 57005 fixme:winsock:convert_socktype_w2u unhandled Windows socket type 57005 fixme:winsock:convert_socktype_w2u unhandled Windows socket type 57005 err:winediag:WSASocketW Failed to create a socket of type SOCK_RAW, this requires special permissions. sock.c:2393: Tests skipped: SOCK_RAW is not supported sock.c:2723: Test succeeded inside todo block: Test[1]: expected 0, got 0

that's a different bug, of course. I commented that out and retried. One more minute gave: ../../../tools/runtest -q -P wine -T ../../.. -M ws2_32.dll -p ws2_32_test.exe.so sock && touch sock.ok fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} fixme:winsock:convert_socktype_w2u unhandled Windows socket type 0 fixme:winsock:WS_EnterSingleProtocolW unknown Protocol <0xffffffff> fixme:winsock:convert_socktype_w2u unhandled Windows socket type 0 fixme:winsock:WS_EnterSingleProtocolW unknown Protocol <0x0000dead> fixme:winsock:convert_socktype_w2u unhandled Windows socket type 0 fixme:winsock:convert_proto_w2u unhandled Windows socket protocol 57005 fixme:winsock:convert_socktype_w2u unhandled Windows socket type 57005 fixme:winsock:convert_socktype_w2u unhandled Windows socket type 57005 err:winediag:WSASocketW Failed to create a socket of type SOCK_RAW, this requires special permissions. sock.c:2393: Tests skipped: SOCK_RAW is not supported sock.c:2715: Test failed: Test[1]: expected 2, got 0 sock.c:2715: Test failed: Test[2]: expected 2, got 0

trying again, 15 minutes: ../../../tools/runtest -q -P wine -T ../../.. -M ws2_32.dll -p ws2_32_test.exe.so sock && touch sock.ok fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} fixme:winsock:convert_socktype_w2u unhandled Windows socket type 0 fixme:winsock:WS_EnterSingleProtocolW unknown Protocol <0xffffffff> fixme:winsock:convert_socktype_w2u unhandled Windows socket type 0 fixme:winsock:WS_EnterSingleProtocolW unknown Protocol <0x0000dead> fixme:winsock:convert_socktype_w2u unhandled Windows socket type 0 fixme:winsock:convert_proto_w2u unhandled Windows socket protocol 57005 fixme:winsock:convert_socktype_w2u unhandled Windows socket type 57005 fixme:winsock:convert_socktype_w2u unhandled Windows socket type 57005 err:winediag:WSASocketW Failed to create a socket of type SOCK_RAW, this requires special permissions. sock.c:2393: Tests skipped: SOCK_RAW is not supported fixme:winsock:convert_socktype_w2u unhandled Windows socket type 999 fixme:winsock:convert_socktype_w2u unhandled Windows socket type 999 fixme:winsock:convert_socktype_w2u unhandled Windows socket type 999 fixme:winsock:convert_socktype_w2u unhandled Windows socket type 999 fixme:winsock:convert_proto_w2u unhandled Windows socket protocol 999 fixme:winsock:convert_proto_w2u unhandled Windows socket protocol 999 fixme:winsock:convert_proto_w2u unhandled Windows socket protocol 999 fixme:winsock:convert_proto_w2u unhandled Windows socket protocol 999 fixme:winsock:convert_socktype_w2u unhandled Windows socket type 999 fixme:winsock:convert_socktype_w2u unhandled Windows socket type 999 fixme:winsock:convert_socktype_w2u unhandled Windows socket type 999 fixme:winsock:convert_socktype_w2u unhandled Windows socket type 999 fixme:winsock:convert_proto_w2u unhandled Windows socket protocol 999 fixme:winsock:convert_proto_w2u unhandled Windows socket protocol 999 fixme:winsock:convert_proto_w2u unhandled Windows socket protocol 999 fixme:winsock:convert_proto_w2u unhandled Windows socket protocol 999 fixme:winsock:WS_getsockopt WS_SO_CONNECT_TIME - faking results sock.c:7512: Tests skipped: Cannot test SIO_ADDRESS_LIST_CHANGE, interactive tests must be enabled fixme:winsock:WSALookupServiceBeginW ((nil) 0x00000000 0x33eaa8) Stub! fixme:winsock:WSALookupServiceBeginW (0x33eb30 0x00000000 (nil)) Stub! fixme:winsock:WSALookupServiceBeginW (0x33eb30 0x00000000 0x33eaa8) Stub! fixme:winsock:WSALookupServiceEnd ((nil)) Stub! fixme:winsock:WSALookupServiceBeginW (0x33eb30 0x00000ff1 0x33eaa8) Stub! fixme:winsock:WSALookupServiceNextW (0xdeadbeef 0x00000000 0x33eaac 0x33eb30) Stub! fixme:winsock:WSALookupServiceEnd (0xdeadbeef) Stub! sock.c:7798: Test succeeded inside todo block: GetQueuedCompletionStatus returned 0 sock.c:7799: Test succeeded inside todo block: Last error was 64

wine-1.7.46-193-g8b566b1

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

WineHQ Bugzilla

12 May 12 May

6:47 p.m.

New subject: [Bug 31927] ws2_32:sock fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0'

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

François Gouget fgouget@codeweavers.com changed:

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

WineHQ Bugzilla

7:03 p.m.

New subject: [Bug 31927] ws2_32:sock fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0'

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

Zebediah Figura z.figura12@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com

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

WineHQ Bugzilla

4 Dec 4 Dec

3:36 p.m.

New subject: [Bug 31927] ws2_32:sock fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0'

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

--- Comment #3 from François Gouget fgouget@codeweavers.com --- This failure has not happened in the past 6 months of nightly WineTest runs. Is it still present?

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

WineHQ Bugzilla

14 Dec 14 Dec

7:51 p.m.

New subject: [Bug 31927] ws2_32:sock fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0'

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

Austin English austinenglish@gmail.com changed:

--- Comment #4 from Austin English austinenglish@gmail.com --- (In reply to François Gouget from comment #3)

...

This failure has not happened in the past 6 months of nightly WineTest runs. Is it still present?

I can't reproduce in 100k tries.

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

WineHQ Bugzilla

7:55 p.m.

New subject: [Bug 31927] ws2_32:sock fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0'

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

Zeb Figura z.figura12@gmail.com changed:

--- Comment #5 from Zeb Figura z.figura12@gmail.com --- FWIW, the relevant test was fixed properly by https://source.winehq.org/git/wine.git/commitdiff/f234341ca1170a799d03179061914b772d4166cd.

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

WineHQ Bugzilla

21 Dec 21 Dec

9:19 p.m.

New subject: [Bug 31927] ws2_32:sock fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0'

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

Alexandre Julliard julliard@winehq.org changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED

--- Comment #6 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 8.0-rc2.

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

736

Age (days ago)

4461

Last active (days ago)

wine-bugs@winehq.org

10 comments

2 participants

tags (0)

participants (2)

wine-bugs＠winehq.org
WineHQ Bugzilla