Updates:
Summary: WatchdogTest.AlarmTest hangs for five minutes, then is killed?
Comment #2 on issue 9194 by [email protected]: WatchdogTest.AlarmTest hangs
for five minutes, then is killed?
http://code.google.com/p/chromium/issues/detail?id=9194
This test just timed out on a non-valgrind trybot:
[ RUN ] WatchdogTest.AlarmTest
[1686:1689:0324/051545:1094147760653:INFO:/b/slave/linux/build/src/base/watchdog.cc(126)]
Watchdog
active: Enabled Watchdog
[1686:1689:0324/051545:1094147771227:INFO:/b/slave/linux/build/src/base/watchdog.h(48)]
Watchdog
alarmed for Enabled
command timed out: 300 seconds without output, killing pid 1684
This was a worse outcome than under valgrind; the whole test was killed.
It seems the test is just plain flaky on our buildbots, valgrind just makes
it more obvious?
--
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
-~----------~----~----~----~------~----~------~--~---
