Re: [1/2] ws2_32/tests: Fix an ok() call comment

[Marvin]

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

Your paranoid android.


=== wxppro (32 bit sock) ===
sock.c:519: Test failed: oob_server (408): unexpectedly at the OOB mark: 0

=== w2008s64 (32 bit sock) ===
sock.c:509: Test failed: oob_server (bb8): unexpectedly at the OOB mark: 0
sock.c:519: Test failed: oob_server (bb8): unexpectedly at the OOB mark: 0

=== w7pro64 (32 bit sock) ===
sock.c:528: Test failed: oob_server (6f0): not at the OOB mark: 1

=== w2008s64 (64 bit sock) ===
sock.c:519: Test failed: oob_server (940): unexpectedly at the OOB mark: 0