Closed Bug 484875 Opened 15 years ago Closed 15 years ago

Spurious timeouts on Windows unit test box

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bzbarsky, Unassigned)

References

Details

(Keywords: intermittent-failure)

The Windows unit test cycle that built m-c revision 3fd33e46a2cd (Mon Mar 23 10:46:41 2009 -0700) went orange with these errors:

buildbot.slave.commands.TimeoutError: command timed out: 300 seconds without output
*** 803 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_bug360437.xul | Test timed out.
*** 830 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_findbar.xul | testNormalFind: find field is not focused
*** 831 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_findbar.xul | testNormalFind: failed to find 'text tes'
*** 838 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_findbar.xul | Case Sensitive label was not correctly updated
*** 839 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_findbar.xul | Test timed out.
*** 842 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_keys.xul | Test timed out.
*** 845 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_largemenu.xul | Test timed out.
*** 846 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_largemenu.xul | Too many test timeouts, giving up.
803 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_bug360437.xul | Test timed out.
830 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_findbar.xul | testNormalFind: find field is not focused
831 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_findbar.xul | testNormalFind: failed to find 'text tes'
838 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_findbar.xul | Case Sensitive label was not correctly updated
839 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_findbar.xul | Test timed out.
842 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_keys.xul | Test timed out.
845 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_largemenu.xul | Test timed out.
846 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/toolkit/content/tests/chrome/test_largemenu.xul | Too many test timeouts, giving up.
make: *** [mochitest-chrome] Error 1
Unknown Error: command finished with exit code: 2

The next cycle went green with no changes to relevant code.  So this was a pure machine load issue, as far as I can see.
This build ran on moz2-win32-slave10, which was migrated from one ESX host to another at 13:10 PDT (bm-vmware03 to 06). That was 40 minutes into the mochitest-plain run but 25 minutes before it gave up, so I don't think it was the short pause for the migration causing the problem. Load on the destination host looks OK, but the data is fairly low resolution. We need to catch one of these in the act to figure out what's happening.
Nick - are you watching for this issue?  Would it be appropriate to assign the bug to you?
As far as I can see this error hasn't repeated, and timeouts on win/linux are occuring at much the same rate as on Mac.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
Whiteboard: [orange]
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.