Re: ws2_32/tests: Mark a SIOCATMARK test result as broken

[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=5238

Your paranoid android.

=== wxppro (32 bit sock) ===
sock: unhandled exception c0000005 at 00000000

=== wvistau64 (32 bit sock) ===
sock: unhandled exception c0000005 at 00000000

=== w2008s64 (64 bit sock) ===
sock: unhandled exception c0000005 at 000007FEFE4220C0

=== w7pro64 (64 bit sock) ===
sock.c:622: Test failed: oob_server (98c): not at the OOB mark: 1