ws2_32: Avoid an unhandled read exception on WSAIoctl
Marvin
testbot at testbot.winehq.org
Thu Sep 1 14:56:54 CDT 2011
Hi,
While running your changed tests on Windows, 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
http://testbot.winehq.org/JobDetails.pl?Key=13899
Your paranoid android.
=== WVISTAADM (32 bit sock) ===
sock.c:2968: Test failed: expected WSAEINVAL, got 10014 instead
=== W2K8SE (32 bit sock) ===
sock.c:2968: Test failed: expected WSAEINVAL, got 10014 instead
=== W7PRO (32 bit sock) ===
sock.c:2968: Test failed: expected WSAEINVAL, got 10014 instead
=== W7PROX64 (32 bit sock) ===
sock.c:2968: Test failed: expected WSAEINVAL, got 10014 instead
=== W7PROX64 (64 bit sock) ===
sock.c:2968: Test failed: expected WSAEINVAL, got 10014 instead
More information about the wine-devel
mailing list