Closed Bug 1507029 Opened 7 years ago Closed 6 years ago

Intermittent TEST-UNEXPECTED-TIMEOUT | devtools/client/webconsole/test/mochitest/browser_webconsole_object_in_sidebar_keyboard_nav.js | application timed out after 370 seconds with no output

Categories

(DevTools :: Console, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure)

Filed by: btara [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=211571589&repo=autoland https://queue.taskcluster.net/v1/task/e5By8F-ySsS7NUEIRTjGgg/runs/1/artifacts/public/logs/live_backing.log task 2018-11-14T01:07:07.776Z] 01:07:07 INFO - TEST-PASS | devtools/client/webconsole/test/mochitest/browser_webconsole_object_in_sidebar_keyboard_nav.js | `b` node is focused again - [task 2018-11-14T01:07:07.776Z] 01:07:07 INFO - Select another object in the console output [task 2018-11-14T01:07:07.776Z] 01:07:07 INFO - Buffered messages logged at 01:00:25 [task 2018-11-14T01:07:07.777Z] 01:07:07 INFO - Matched a message with text: "Array", all messages received. [task 2018-11-14T01:07:07.777Z] 01:07:07 INFO - Buffered messages logged at 01:00:29 [task 2018-11-14T01:07:07.778Z] 01:07:07 INFO - Waiting for event: 'popuphidden' on [object XULPopupElement]. [task 2018-11-14T01:07:07.778Z] 01:07:07 INFO - Got event: 'popuphidden' on [object XULPopupElement]. [task 2018-11-14T01:07:07.779Z] 01:07:07 INFO - Buffered messages logged at 01:00:35 [task 2018-11-14T01:07:07.779Z] 01:07:07 INFO - TEST-PASS | devtools/client/webconsole/test/mochitest/browser_webconsole_object_in_sidebar_keyboard_nav.js | The root node of the new object in the sidebar is focused - [task 2018-11-14T01:07:07.779Z] 01:07:07 INFO - Leaving test bound [task 2018-11-14T01:07:07.780Z] 01:07:07 INFO - Buffered messages finished [task 2018-11-14T01:07:07.780Z] 01:07:07 ERROR - TEST-UNEXPECTED-TIMEOUT | devtools/client/webconsole/test/mochitest/browser_webconsole_object_in_sidebar_keyboard_nav.js | application timed out after 370 seconds with no output [task 2018-11-14T01:07:07.781Z] 01:07:07 ERROR - Force-terminating active process(es). [task 2018-11-14T01:07:07.786Z] 01:07:07 INFO - Determining child pids from psutil... [task 2018-11-14T01:07:07.786Z] 01:07:07 INFO - [3078, 3037, 2934, 2952, 3007] [task 2018-11-14T01:07:07.786Z] 01:07:07 INFO - ==> process 2844 launched child process 2867 [task 2018-11-14T01:07:07.786Z] 01:07:07 INFO - ==> process 2844 launched child process 2934 [task 2018-11-14T01:07:07.786Z] 01:07:07 INFO - ==> process 2844 launched child process 2952 [task 2018-11-14T01:07:07.786Z] 01:07:07 INFO - ==> process 2844 launched child process 3007 [task 2018-11-14T01:07:07.794Z] 01:07:07 INFO - ==> process 2844 launched child process 3037 [task 2018-11-14T01:07:07.794Z] 01:07:07 INFO - ==> process 2844 launched child process 3078 [task 2018-11-14T01:07:07.794Z] 01:07:07 INFO - Found child pids: set([3078, 2952, 2867, 2934, 3037, 3007]) [task 2018-11-14T01:07:07.795Z] 01:07:07 INFO - Failed to get child procs [task 2018-11-14T01:07:07.795Z] 01:07:07 INFO - Killing process: 3078 [task 2018-11-14T01:07:07.795Z] 01:07:07 INFO - TEST-INFO | started process screentopng [task 2018-11-14T01:07:53.225Z] 01:07:53 INFO - TEST-INFO | screentopng: exit 0
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Status: REOPENED → RESOLVED
Closed: 7 years ago6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.