[PATCH 2/2] kernel32/tests: Verify the stability of CreateTimerQueue.

Joerg-Cyril.Hoehle at t-systems.com Joerg-Cyril.Hoehle at t-systems.com
Thu Feb 14 06:38:56 CST 2013


I'm not at all eager to provoke random test failures on testbot, but is not writing tests the solution?
If I don't stress the timers, how can I show how it behaves?

Testbot simply *will* introduce random delays so large that the average gets boosted too much, e.g.
sync.c:625: thread 2804 hpctime  700 delta 326 (instead of 31-32)
sync.c:1055: Test failed: TimerQueue period 48.556<->22

I'm open for any suggestion. If you remember past test submission, you'll note that I have considerably
reduced the number of timer runs such that errors should be less frequent.
(Adding more cases increases the winetest log by 1-2KB each time...)

See http://testbot.winehq.org/JobDetails.pl?Key=24398
for 3 failures from 31 machines. I'm not counting
sync.c:1015: Test failed: DeleteTimerQueueTimer
I believe Francois Gouget once investigated that one.

Should I just trace() the values without ok() s.t. curious people can look at it?

 Jörg Höhle
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-kernel32-tests-Verify-the-stability-of-CreateTimerQ.patch
Type: application/octet-stream
Size: 7330 bytes
Desc: 0002-kernel32-tests-Verify-the-stability-of-CreateTimerQ.patch
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20130214/779b995f/attachment-0001.obj>

More information about the wine-patches mailing list