[1/7] ntdll/tests: Use longer waits to reduce risk of random failures on the testbot.

Sebastian Lackner sebastian at fds-team.de
Sat Aug 20 15:03:47 CDT 2016


On 20.08.2016 21:26, Marvin wrote:
> 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
> https://testbot.winehq.org/JobDetails.pl?Key=25284
> 
> Your paranoid android.
> 
> 
> === w7u (32 bit threadpool) ===
> threadpool.c:367: Test failed: WaitForSingleObject returned 258
> threadpool.c:379: Test failed: expected info.userdata = 0x10000, got 0
> threadpool.c:390: Test failed: expected info.userdata = 0x10000, got 0
> threadpool.c:409: Test failed: expected info.userdata = 1, got 0
> threadpool.c:422: Test failed: expected info.userdata = 1, got 0
> threadpool.c:424: Test failed: expected STATUS_PENDING, got 0
> threadpool.c:427: Test failed: WaitForSingleObject returned 258
> 
> === w864 (64 bit threadpool) ===
> threadpool.c:1618: Test failed: WaitForSingleObject returned 258
> threadpool.c:1619: Test failed: expected result 2, got 0
> threadpool.c:1619: Test failed: expected result 4, got 2
> threadpool.c:1619: Test failed: expected result 6, got 4
> threadpool.c:1619: Test failed: expected result 8, got 6
> threadpool.c:1619: Test failed: expected result 10, got 8
> threadpool.c:1619: Test failed: expected result 12, got 10
> threadpool.c:1619: Test failed: expected result 14, got 12
[...]

Too bad, I was hoping to fix all random failures. :( Nevertheless, this
patch should still be an improvement. The test failures are not present
in any of the following 4 test runs. Is there anything what could cause
the testbot to freeze for a short time?




More information about the wine-devel mailing list