[1/3] ws2_32/tests: Fix an ok() call comment
Marvin
testbot at winehq.org
Sat Sep 28 10:19:47 CDT 2013
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=2392
Your paranoid android.
=== wxppro (32 bit sock) ===
sock.c:519: Test failed: oob_server (748): unexpectedly at the OOB mark: 0
=== w2008s64 (32 bit sock) ===
sock.c:519: Test failed: oob_server (998): unexpectedly at the OOB mark: 0
sock: unhandled exception c0000005 at 00000000
=== w7pro64 (32 bit sock) ===
sock.c:509: Test failed: oob_server (2f0): unexpectedly at the OOB mark: 0
sock.c:519: Test failed: oob_server (2f0): unexpectedly at the OOB mark: 0
sock.c:288: Test failed: do_synchronous_recv (2f0): error 10054:
sock.c:534: Test failed: oob_server (2f0): not at the OOB mark: 1
=== w2008s64 (64 bit sock) ===
sock.c:509: Test failed: oob_server (938): unexpectedly at the OOB mark: 0
sock.c:519: Test failed: oob_server (938): unexpectedly at the OOB mark: 0
sock: unhandled exception c0000005 at 000007FEFE229CD9
More information about the wine-devel
mailing list