Closed Bug 830201 Opened 11 years ago Closed 11 years ago

Intermittent test_healthreporter.js "command timed out: 1200 seconds without output, attempting to kill"

Categories

(Firefox Health Report Graveyard :: Client: Desktop, defect, P2)

Product:
Firefox Health Report Graveyard
Component:
Client: Desktop
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure) 

https://tbpl.mozilla.org/php/getParsedLog.php?id=18650035&tree=Services-Central
Rev3 WINNT 6.1 services-central debug test xpcshell on 2013-01-09 14:36:17 PST for push ffd1635a8f79
slave: talos-r3-w7-052

TEST-INFO | c:\talos-slave\test\build\xpcshell\tests\services\healthreport\tests\xpcshell\test_healthreporter.js | running test ...

command timed out: 1200 seconds without output, attempting to kill
SIGKILL failed to kill process
I suspect this is a dupe of bug 830145 and/or bug 828149. We'll figure out how all the bugs fall out.
This will be impossible to debug with the test runner buffering output.

If we're lucky, bug 828149 will have solved this issue. Time will tell.
Buffering of test output: Bug 804648.
OS: Windows 7 → All
Hardware: x86 → All
We added try..finally blocks to tests in this file so we hopefully shouldn't see this timeouts any more. We should close this after a few more days. The failures will surface as a separate signature (like bug 850091).
Priority: -- → P2
Whiteboard: [closeme 2013-03-31]
We uplifted to Aurora the patch fixing these timeouts. I'm confident we can close this one earlier than scheduled and we won't see any more timeouts.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Whiteboard: [closeme 2013-03-31]
Component: Metrics and Firefox Health Report → Client: Desktop
Product: Mozilla Services → Firefox Health Report
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in before you can comment on or make changes to this bug.