Re: [3/3] ws2_32: Implement WSASendMsg() (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 https://newtestbot.winehq.org/JobDetails.pl?Key=2393 Your paranoid android. === wxppro (32 bit sock) === sock.c:519: Test failed: oob_server (1d0): unexpectedly at the OOB mark: 0 === w2008s64 (32 bit sock) === sock.c:519: Test failed: oob_server (5a0): unexpectedly at the OOB mark: 0 === w2008s64 (64 bit sock) === sock.c:509: Test failed: oob_server (b64): unexpectedly at the OOB mark: 0 sock.c:519: Test failed: oob_server (b64): unexpectedly at the OOB mark: 0 === w7pro64 (64 bit sock) === sock.c:509: Test failed: oob_server (650): unexpectedly at the OOB mark: 0 sock.c:519: Test failed: oob_server (650): unexpectedly at the OOB mark: 0 sock.c:288: Test failed: do_synchronous_recv (650): error 10054: sock.c:534: Test failed: oob_server (650): not at the OOB mark: 1
participants (1)
-
Marvin