[PATCH] ws2_32: Add a suitable break in the loop for WSASocketW.
15 Mar
15 Mar
3:34 a.m.
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=86985 Your paranoid android. === debiant2 (64 bit WoW report) === ws2_32: sock.c:2852: Test failed: Test[1]: expected 2, got 0 sock.c:2852: Test failed: Test[2]: expected 2, got 0 sock.c:2852: Test failed: Test[1]: expected 2, got 0 sock.c:2852: Test failed: Test[2]: expected 2, got 0
1741
Age (days ago)
1741
Last active (days ago)
1 comments
2 participants
participants (2)
-
Jiangyi Chen -
Marvin