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

[Bruno Jesus]

On Thu, Feb 27, 2014 at 11:33 AM, André Hentschel  wrote:
> dlls/ws2_32/tests/sock.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/dlls/ws2_32/tests/sock.c b/dlls/ws2_32/tests/sock.c
> index 2252245..3f27b02 100644
> --- a/dlls/ws2_32/tests/sock.c
> +++ b/dlls/ws2_32/tests/sock.c
> @@ -610,7 +610,7 @@ static VOID WINAPI oob_server ( server_params *par )
>      ok ( pos == -1, "simple_server (%x): test pattern error: %d\n", id, pos);
>  ioctlsocket ( mem->sock[0].s, SIOCATMARK, &atmark );
> - ok ( atmark == 1, "oob_server (%x): unexpectedly at the OOB mark: %i\n", id, atmark );
> - ok ( atmark == 1 || broken(atmark == 0), "oob_server (%x): unexpectedly at the OOB mark: %i\n", id, atmark );

There is other test failing too, right? At least for me. So this would
only "solve" half of the problem.
What we need to do IMO is simplify the test using a more sequential
way to ensure normal and OOB data does not get mixed.

Regards,
Bruno