5 Jul
2015
5 Jul
'15
1:10 a.m.
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=15039
Your paranoid android.
=== w7u (32 bit threadpool) ===
threadpool.c:734: Test failed: WaitForSingleObject returned 258
5 Jul
5 Jul
3:11 a.m.
New subject: [4/7] ntdll/tests: Add basic tests for threadpool wait objects.
On 05.07.2015 03:10, 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=15039
Your paranoid android.
=== w7u (32 bit threadpool) ===
threadpool.c:734: Test failed: WaitForSingleObject returned 258
This is again a random failure and not present in a second run (and also not in patch
5/7):
https://newtestbot.winehq.org/JobDetails.pl?Key=15041
On a real Win 7 machine the tests reliably succeed. Is there anything wrong with the
testbot
(or especially the Win 7 VM) that timer related tests are so unreliable? :/
3235
days inactive
3235
days old
1 comments
2 participants
participants (2)
-
Marvin -
Sebastian Lackner