Intermittent TEST-UNEXPECTED-CRASH | /url/failure.html | expected OK
Categories
(Core :: DOM: Networking, defect, P3)
Tracking
()
People
(Reporter: intermittent-bug-filer, Unassigned)
Details
(Keywords: intermittent-failure, regression, Whiteboard: [necko-triaged])
Filed by: ncsoregi [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=256797277&repo=autoland
Full log: https://queue.taskcluster.net/v1/task/P0m7pUYoRqqRA5RIo39Thw/runs/0/artifacts/public/logs/live_backing.log
[task 2019-07-16T20:50:08.803Z] 20:50:08 INFO - TEST-START | /url/failure.html
[task 2019-07-16T20:50:08.818Z] 20:50:08 INFO - Closing window 26
[task 2019-07-16T20:55:09.481Z] 20:55:09 INFO - IOError on command, setting status to CRASH
[task 2019-07-16T20:55:09.710Z] 20:55:09 INFO - TEST-UNEXPECTED-CRASH | /url/failure.html | expected OK
[task 2019-07-16T20:55:09.710Z] 20:55:09 INFO - TEST-INFO took 300903ms
![]() |
||
Comment 1•6 years ago
|
||
"IOError on command, setting status to CRASH" - can we get some more info beyond this? note that this happened 5 minutes after the test start (no meaningful output in between).
CC'in valentin for thoughts.
Comment hidden (Intermittent Failures Robot) |
Updated•6 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 5•5 years ago
|
||
There really isn't much to go on with this bug.
The reason for the timeout is either that the tests fails to load for some (Android related?) reason, or that this fetch doesn't resolve.
Comment 6•4 years ago
|
||
Bulk closing some old intermittents.
Description
•