Hi,
While running your changed tests, 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://testbot.winehq.org/JobDetails.pl?Key=62679
Your paranoid android.
=== debian10 (32 bit report) ===
kernel32: sync.c:2371: Test failed: thread commands were executed in the wrong order (occurred 9 times). sync.c:2375: Test failed: AcquireSRWLockExclusive didn't block when called multiple times from the same thread (occurred 2 times). sync.c:2379: Test failed: AcquireSRWLockShared didn't block when the same thread holds an exclusive lock (occurred 2 times). sync.c:2383: Test failed: AcquireSRWLockExclusive didn't block when the same thread holds a shared lock (occurred 2 times). sync.c:2387: Test failed: AcquireSRWLockExclusive didn't block when a second thread holds the exclusive lock (occurred 2 times). sync.c:2391: Test failed: thread waiting for exclusive access to the SHMLock was not preferred (occurred 2 times).
=== debian10 (32 bit French report) ===
kernel32: sync.c:2371: Test failed: thread commands were executed in the wrong order (occurred 11 times). sync.c:2375: Test failed: AcquireSRWLockExclusive didn't block when called multiple times from the same thread (occurred 2 times). sync.c:2379: Test failed: AcquireSRWLockShared didn't block when the same thread holds an exclusive lock (occurred 2 times). sync.c:2383: Test failed: AcquireSRWLockExclusive didn't block when the same thread holds a shared lock (occurred 2 times). sync.c:2387: Test failed: AcquireSRWLockExclusive didn't block when a second thread holds the exclusive lock (occurred 2 times). sync.c:2391: Test failed: thread waiting for exclusive access to the SHMLock was not preferred (occurred 3 times).
=== debian10 (32 bit Japanese:Japan report) ===
kernel32: sync.c:2371: Test failed: thread commands were executed in the wrong order (occurred 9 times). sync.c:2375: Test failed: AcquireSRWLockExclusive didn't block when called multiple times from the same thread (occurred 2 times). sync.c:2379: Test failed: AcquireSRWLockShared didn't block when the same thread holds an exclusive lock (occurred 2 times). sync.c:2383: Test failed: AcquireSRWLockExclusive didn't block when the same thread holds a shared lock (occurred 2 times). sync.c:2387: Test failed: AcquireSRWLockExclusive didn't block when a second thread holds the exclusive lock (occurred 2 times). sync.c:2391: Test failed: thread waiting for exclusive access to the SHMLock was not preferred (occurred 2 times).
=== debian10 (32 bit Chinese:China report) ===
kernel32: sync.c:2371: Test failed: thread commands were executed in the wrong order (occurred 11 times). sync.c:2375: Test failed: AcquireSRWLockExclusive didn't block when called multiple times from the same thread (occurred 2 times). sync.c:2379: Test failed: AcquireSRWLockShared didn't block when the same thread holds an exclusive lock (occurred 2 times). sync.c:2383: Test failed: AcquireSRWLockExclusive didn't block when the same thread holds a shared lock (occurred 2 times). sync.c:2387: Test failed: AcquireSRWLockExclusive didn't block when a second thread holds the exclusive lock (occurred 2 times). sync.c:2391: Test failed: thread waiting for exclusive access to the SHMLock was not preferred (occurred 3 times).
=== debian10 (32 bit WoW report) ===
kernel32: sync.c:2371: Test failed: thread commands were executed in the wrong order (occurred 9 times). sync.c:2375: Test failed: AcquireSRWLockExclusive didn't block when called multiple times from the same thread (occurred 2 times). sync.c:2379: Test failed: AcquireSRWLockShared didn't block when the same thread holds an exclusive lock (occurred 2 times). sync.c:2383: Test failed: AcquireSRWLockExclusive didn't block when the same thread holds a shared lock (occurred 2 times). sync.c:2387: Test failed: AcquireSRWLockExclusive didn't block when a second thread holds the exclusive lock (occurred 2 times). sync.c:2391: Test failed: thread waiting for exclusive access to the SHMLock was not preferred (occurred 2 times).
=== debian10 (64 bit WoW report) ===
kernel32: sync.c:2371: Test failed: thread commands were executed in the wrong order (occurred 9 times). sync.c:2375: Test failed: AcquireSRWLockExclusive didn't block when called multiple times from the same thread (occurred 2 times). sync.c:2379: Test failed: AcquireSRWLockShared didn't block when the same thread holds an exclusive lock (occurred 2 times). sync.c:2383: Test failed: AcquireSRWLockExclusive didn't block when the same thread holds a shared lock (occurred 2 times). sync.c:2387: Test failed: AcquireSRWLockExclusive didn't block when a second thread holds the exclusive lock (occurred 2 times). sync.c:2391: Test failed: thread waiting for exclusive access to the SHMLock was not preferred (occurred 2 times).