Re: [1/3] server: Add a process flag indicating whether the process is terminating, use it to block thread creation in a bei

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

Your paranoid android.

=== W7PROX64 (64 bit loader) ===
loader.c:1638: Test failed: expected WAIT_OBJECT_0, got 0x102
loader.c:1648: Test failed: expected thread exit code 196, got 259
loader.c:1210: Test failed: expected thread exit code 196, got 259
loader.c:1220: Test failed: expected WAIT_ABANDONED, got 0x102
loader.c:1236: Test failed: expected WAIT_OBJECT_0, got 0x102

[1/3] server: Add a process flag indicating whether the process is terminating, use it to block thread creation in a bei

[Dmitry Timoshkov]

Marvin  wrote:
> === W7PROX64 (64 bit loader) ===
> loader.c:1638: Test failed: expected WAIT_OBJECT_0, got 0x102
> loader.c:1648: Test failed: expected thread exit code 196, got 259
> loader.c:1210: Test failed: expected thread exit code 196, got 259
> loader.c:1220: Test failed: expected WAIT_ABANDONED, got 0x102
> loader.c:1236: Test failed: expected WAIT_OBJECT_0, got 0x102

Something is broken in that VM, the patch doesn't change anything in
the test except removing a todo_wine. And patch [2/3] passes without
failures: https://testbot.winehq.org/JobDetails.pl?Key=25446