[PATCH 1/2] ws2_32/tests: Check if getsockopt returns non-zero protocol for sockets with autoselected protocol
Marvin
testbot at winehq.org
Sun Aug 23 15:27:12 CDT 2020
Hi,
While running your changed tests, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=77475
Your paranoid android.
=== debiant (32 bit report) ===
ws2_32:
sock.c:1765: Test failed: getsockopt returned zero protocol
=== debiant (32 bit French report) ===
ws2_32:
sock.c:1765: Test failed: getsockopt returned zero protocol
=== debiant (32 bit Japanese:Japan report) ===
ws2_32:
sock.c:1765: Test failed: getsockopt returned zero protocol
sock.c:3068: Test failed: Test[1]: expected 2, got 0
sock.c:3068: Test failed: Test[2]: expected 2, got 0
sock.c:3068: Test failed: Test[1]: expected 2, got 0
sock.c:3068: Test failed: Test[2]: expected 2, got 0
=== debiant (32 bit Chinese:China report) ===
ws2_32:
sock.c:1765: Test failed: getsockopt returned zero protocol
=== debiant (32 bit WoW report) ===
ws2_32:
sock.c:1765: Test failed: getsockopt returned zero protocol
=== debiant (64 bit WoW report) ===
ws2_32:
sock.c:1765: Test failed: getsockopt returned zero protocol
More information about the wine-devel
mailing list