[PATCH 2/4] ws2_32: Close all open sockets in WSACleanup().

[Marvin]

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=78516

Your paranoid android.


=== w10pro64_ar (32 bit report) ===

ws2_32:
sock.c:3832: Test failed: expected 1, got 0
sock.c:3837: Test failed: expected 10061, got 0
sock.c:3838: Test failed: fdWrite socket is not in the set

=== w1064v1809 (64 bit report) ===

ws2_32:
sock.c:5921: Test failed: Expected event sequence [FD_WRITE(0)], got []
sock.c:5942: Test failed: Expected event sequence [FD_READ(0) FD_CLOSE(0)], got [FD_READ(0) FD_WRITE(0) FD_CLOSE(10053)]
sock.c:5945: Test failed: Failed to empty buffer: -1 - 10054
sock.c:5946: Test failed: Expected event sequence [FD_READ(0)], got []
sock.c:5949: Test failed: Failed to empty buffer: -1 - 10054