Re: [PATCH 3/4] ws2_32/tests: Test for AcceptEx IOCP behavior for a duplicated handle (try 2).
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=18137 Your paranoid android. === W7PROX64 (64 bit sock) === sock.c:5628: Test failed: Internal status is c120 === TEST64_W7SP1 (64 bit sock) === sock.c:5628: Test failed: Internal status is c120
Re: [PATCH 3/4] ws2_32/tests: Test for AcceptEx IOCP behavior for a duplicated handle.
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=18133 Your paranoid android. === WVISTAADM (32 bit sock) === sock.c:5628: Test failed: Internal status is c120 === W2K8SE (32 bit sock) === sock.c:5628: Test failed: Internal status is c120 === W7PRO (32 bit sock) === sock.c:5628: Test failed: Internal status is c120 === W7PROX64 (32 bit sock) === sock.c:5628: Test failed: Internal status is c120 === TEST64_W7SP1 (32 bit sock) === sock.c:5628: Test failed: Internal status is c120 === W7PROX64 (64 bit sock) === sock.c:5628: Test failed: Internal status is c120 === TEST64_W7SP1 (64 bit sock) === sock.c:5628: Test failed: Internal status is c120