Re: [2/2] ws2_32: Properly implement SO_CONNECT_TIME

[Marvin]

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
https://testbot.winehq.org/JobDetails.pl?Key=7301

Your paranoid android.


=== w2000pro (32 bit sock) ===
sock: unhandled exception c0000005 at 00000000

=== wvistau64 (32 bit sock) ===
sock.c:4244: Test failed: unexpected connect time 0
sock.c:4250: Test failed: unexpected connect time 0

=== w2008s64 (32 bit sock) ===
sock.c:4244: Test failed: unexpected connect time 0
sock.c:4250: Test failed: unexpected connect time 0

=== w7u (32 bit sock) ===
sock.c:4244: Test failed: unexpected connect time 0
sock.c:4250: Test failed: unexpected connect time 0

=== w8 (32 bit sock) ===
sock.c:4244: Test failed: unexpected connect time 0
sock.c:4250: Test failed: unexpected connect time 0

=== wvistau64 (64 bit sock) ===
sock.c:4244: Test failed: unexpected connect time 0
sock.c:4250: Test failed: unexpected connect time 0

=== w2008s64 (64 bit sock) ===
sock.c:4244: Test failed: unexpected connect time 0
sock.c:4250: Test failed: unexpected connect time 0