Closed Bug 967352 Opened 12 years ago Closed 11 years ago

dromaeo-metro "command timed out: 3600 seconds without output, attempting to kill", "timed out after 3600 seconds of no output", "command timed out: 7200 seconds elapsed, attempting to kill"

Categories

(Testing :: Talos, defect)

x86
Windows 8
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: philor, Unassigned)

References

Details

Kind of surprised we've never been bitten by not having PGO on Cedar before this. https://tbpl.mozilla.org/php/getParsedLog.php?id=34033418&tree=Mozilla-Central WINNT 6.2 mozilla-central pgo talos dromaeojs-metro on 2014-02-03 15:56:20 PST for push 067123df4f77 slave: t-w864-ix-004 15:59:31 INFO - DEBUG : command line: C:\slave\test-pgo\build\application\firefox\metrotestharness -profile c:\users\cltbld~1.t-w\appdata\local\temp\tmpyekigj\profile http://localhost/getInfo.html 16:59:31 INFO - mozprocess timed out 16:59:31 ERROR - timed out after 3600 seconds of no output 16:59:31 ERROR - Return code: 259 16:59:31 ERROR - # TBPL FAILURE # 16:59:31 INFO - Running post-action listener: _resource_record_post_action 16:59:31 INFO - Running post-run listener: _resource_record_post_run 16:59:32 INFO - Total resource usage - Wall time: 3603s; CPU: 0.0%; Read bytes: 433998848; Write bytes: 114558464; Read time: 11868600; Write time: 1640060 16:59:32 INFO - install - Wall time: 2s; CPU: 13.0%; Read bytes: 0; Write bytes: 1975296; Read time: 0; Write time: 54950 16:59:32 INFO - run-tests - Wall time: 3601s; CPU: 0.0%; Read bytes: 433986560; Write bytes: 102481920; Read time: 11866310; Write time: 1303720 16:59:32 INFO - Running post-run listener: _upload_blobber_files 16:59:32 INFO - Blob upload gear active. 16:59:32 INFO - There are no files to upload in the directory. Skipping the blob upload mechanism ... 16:59:32 INFO - Copying logs to upload dir... 16:59:32 INFO - mkdir: C:\slave\test-pgo\build\upload\logs command timed out: 7200 seconds elapsed, attempting to kill SIGKILL failed to kill process Which means that every single PGO build results in wasting two hours of a Windows test slave's time. We haven't actually finished a Windows build on Aurora yet, but... every build on Aurora is PGO.
Actually, I'm not sure it's permapurple on PGO, since I'm not entirely willing to waste 20 hours of Win8 test slave time triggering ten runs, and I am sure that both some PGO runs and a fair number of non-PGO runs are hitting "command timed out: 3600 seconds without output, attempting to kill" either before or instead of the mozprocess timeout, so let's just pile them up, and let... someone sort them out.
Summary: dromaeo-metro on PGO builds is permapurple with "timed out after 3600 seconds of no output" and "command timed out: 7200 seconds elapsed, attempting to kill" → dromaeo-metro "command timed out: 3600 seconds without output, attempting to kill", "timed out after 3600 seconds of no output", "command timed out: 7200 seconds elapsed, attempting to kill"
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.