84611 2012-04-23 10:34:00 -0700 EWS bots have no timeout protection for the c++ unittests 2014-10-10 14:48:45 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified NEW P2 Normal --- 1 eric webkit-unassigned abarth ap eric gavinp jake.nielsen.webkit jamesr spena oldest_to_newest 607813 0 eric 2012-04-23 10:34:00 -0700 All Chromium EWS bots are hung running unit tests I guess the c++ unittests have no hang protection. [----------] 8 tests from TreeSynchronizerTest [ RUN ] TreeSynchronizerTest.syncNullTree [ OK ] TreeSynchronizerTest.syncNullTree (0 ms) [ RUN ] TreeSynchronizerTest.syncSimpleTreeFromEmpty [ OK ] TreeSynchronizerTest.syncSimpleTreeFromEmpty (0 ms) [ RUN ] TreeSynchronizerTest.syncSimpleTreeReusingLayers (hang here forever) Some patch 1.5 days ago hung all the bots. Still figuring out which patch. :) 607817 1 eric 2012-04-23 10:35:44 -0700 cr-linux #1 is hung processing bug 84524. 607822 2 eric 2012-04-23 10:42:03 -0700 Same hang for cr-linux-3: [----------] 8 tests from TreeSynchronizerTest [ RUN ] TreeSynchronizerTest.syncNullTree [ OK ] TreeSynchronizerTest.syncNullTree (0 ms) [ RUN ] TreeSynchronizerTest.syncSimpleTreeFromEmpty [ OK ] TreeSynchronizerTest.syncSimpleTreeFromEmpty (0 ms) [ RUN ] TreeSynchronizerTest.syncSimpleTreeReusingLayers Was also hung on bug 84524 607829 3 jamesr 2012-04-23 10:47:57 -0700 The googletest harness doesn't have appear to have a built-in test timeout mechanism: http://code.google.com/p/googletest/issues/detail?id=348, so this would probably have to be written in the python layer. We run the unit tests in a child process so that probably wouldn't be too hard.