Re: [PATCH 1/3] server: certain access flags are illegal for OpenMutex

[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
http://testbot.winehq.org/JobDetails.pl?Key=14233

Your paranoid android.


=== WNT4WSSP6 (32 bit sync) ===
sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5

=== W2KPROSP4 (32 bit sync) ===
sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5

=== WXPPROSP3 (32 bit sync) ===
sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5

=== W2K3R2SESP2 (32 bit sync) ===
sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5

=== WVISTAADM (32 bit sync) ===
sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5

=== W2K8SE (32 bit sync) ===
sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5

=== W7PRO (32 bit sync) ===
sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5

=== W7PROX64 (32 bit sync) ===
sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5

=== W7PROX64 (64 bit sync) ===
sync.c:174: Test failed: ReleaseMutex should have failed with ERROR_NOT_OWNER instead of 5