Re: [PATCH 1/6] ws2_32: Mark WinNT 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=2061

Your paranoid android.

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

[PATCH 1/6] ws2_32: Mark WinNT result as broken

[Bruno Jesus]

On Sun, Sep 8, 2013 at 1:58 AM, Marvin  wrote:
> 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=2061
>
> Your paranoid android.
>
> === wxppro (32 bit sock) ===
> sock.c:519: Test failed: oob_server (7e0): unexpectedly at the OOB mark: 0

All socket tests are suffering from this more often in the new test
bot. In [1] there is a clean run of all tests, in the next days I'll
look for a way to eliminate this error by updating the tests.

[1] https://testbot.winehq.org/JobDetails.pl?Key=26990

Regards,
Bruno