Comment #2 on issue 5723 by [email protected]: WatchdogTest.AlarmTest
has timing issues
http://code.google.com/p/chromium/issues/detail?id=5723
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=7744
------------------------------------------------------------------------
r7744 | [email protected] | 2009-01-08 10:29:20 -0800 (Thu, 08 Jan 2009) | 14
lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/watchdog_unittest.cc?r1=7744&r2=7743
Significantly increase timeouts to reduce flakiness
Several tests now "plan for success" and will terminate rapidly if all goes
well (and will hang if there really is a problem).
One test I just upped by a factor of 5, hoping that I'll get a timem slice
within a 5 second window, rather than assuming that I'll get one within
a 1 second window. I could go further, but the test now takes over 5
seconds
to run, which seems like a lot of time for a trivial test.
bug=5723
r=maruel
Review URL: http://codereview.chromium.org/16495
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
