Closed
Bug 1322362
Opened 8 years ago
Closed 8 years ago
Intermittent Autophone remoteautomation.py | application timed out after 330 seconds with no output
Categories
(Testing Graveyard :: Autophone, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1308560
People
(Reporter: intermittent-bug-filer, Unassigned)
Details
(Keywords: intermittent-failure)
Filed by: philringnalda [at] gmail.com
https://treeherder.mozilla.org/logviewer.html#?job_id=5825835&repo=mozilla-central
https://autophone.s3.amazonaws.com/v1/task/I5Gw8lkqQMW7NVPzsU1ywA/runs/0/artifacts/public/build/mochitest-toolkit-widgets-mochitests-toolkit-widgets-settings.ini-1-nexus-5-5-fc5a8463-b620-4b80-8fd7-3c327d171bc1.log
Comment 1•8 years ago
|
||
Phil, Have you seen more of these? Can we resolve it now?
Flags: needinfo?(philringnalda)
Comment 2•8 years ago
|
||
There was one on December 29th, starred as bug 1308560 because for that bug I eventually (two days after filing this) remembered the byzantine way that you have to include TEST-UNEXPECTED-FAIL in the bug summary for failures which are reported as happening in remoteautomation.py, since treeherder blacklists that as a "test filename" and falls back to a full-line search which includes the T-U-F, so as-is this bug would never be suggested.
I don't have any personal need to track autophone startup hangs separate from emulator startup hangs, so let's just use that one.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(philringnalda)
Resolution: --- → DUPLICATE
Updated•3 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•