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=25479
Your paranoid android.
=== TEST64_W7SP1 (32 bit loader) === loader.c:1210: Test failed: expected thread exit code 195, got 259 loader.c:1210: Test failed: expected thread exit code 195, got 259 loader.c:1220: Test failed: expected WAIT_ABANDONED, got 0x102 loader.c:1236: Test failed: expected WAIT_OBJECT_0, got 0x102 loader.c:1238: Test failed: expected WAIT_OBJECT_0, got 0x102
Marvin testbot@testbot.winehq.org wrote:
=== TEST64_W7SP1 (32 bit loader) === loader.c:1210: Test failed: expected thread exit code 195, got 259 loader.c:1210: Test failed: expected thread exit code 195, got 259 loader.c:1220: Test failed: expected WAIT_ABANDONED, got 0x102 loader.c:1236: Test failed: expected WAIT_OBJECT_0, got 0x102 loader.c:1238: Test failed: expected WAIT_OBJECT_0, got 0x102
Testbot for some reason failed again in the test which passes before and after this single run. Here is the result of this same patch which passes: https://testbot.winehq.org/JobDetails.pl?Key=25477 (Additional trace() statements were added while I was looking for that CloseHandle() call which leads to premature process termination under some Windows versions.)
Subsequent test runs in this patch set also finish without failures.
-
Dmitry Timoshkov -
Marvin