NEW 84611
EWS bots have no timeout protection for the c++ unittests 
https://bugs.webkit.org/show_bug.cgi?id=84611
Summary EWS bots have no timeout protection for the c++ unittests
Eric Seidel (no email)
Reported 2012-04-23 10:34:00 PDT
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. :)
Attachments
Add attachment proposed patch, testcase, etc.
Eric Seidel (no email)
Comment 1 2012-04-23 10:35:44 PDT
cr-linux #1 is hung processing bug 84524.
Eric Seidel (no email)
Comment 2 2012-04-23 10:42:03 PDT
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
James Robinson
Comment 3 2012-04-23 10:47:57 PDT
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.
Note You need to log in before you can comment on or make changes to this bug.