Closed Bug 1578923 Opened 6 years ago Closed 6 years ago

Intermittent devtools/client/webconsole/test/browser/browser_webconsole_telemetry_jump_to_definition.js | A promise chain failed to handle a rejection: this.panelWin is null - stack: DebuggerPanel@resource://devtools/client/debugger/panel.js:18:3

Categories

(DevTools :: Console, defect, P5)

Product:
DevTools
Component:
Console
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1559854

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure, regression)

Filed by: ncsoregi [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=265016777&repo=autoland
Full log: https://queue.taskcluster.net/v1/task/fURUKsxlS3qVgL0fNxQwzQ/runs/0/artifacts/public/logs/live_backing.log

entering test: devtools/client/webconsole/test/browser/browser_webconsole_telemetry_jump_to_definition.js

[task 2019-09-04T21:32:39.802Z] 21:32:39 INFO - TEST-PASS | devtools/client/webconsole/test/browser/browser_webconsole_telemetry_jump_to_definition.js | There was 1 event logged -
[task 2019-09-04T21:32:39.802Z] 21:32:39 INFO - TEST-PASS | devtools/client/webconsole/test/browser/browser_webconsole_telemetry_jump_to_definition.js | There is a valid session_id in the logged event -
[task 2019-09-04T21:32:39.802Z] 21:32:39 INFO - Leaving test bound
[task 2019-09-04T21:32:39.802Z] 21:32:39 INFO - Buffered messages logged at 21:32:39
[task 2019-09-04T21:32:39.802Z] 21:32:39 INFO - Removing tab.
[task 2019-09-04T21:32:39.802Z] 21:32:39 INFO - Waiting for event: 'TabClose' on [object XULElement].
[task 2019-09-04T21:32:39.803Z] 21:32:39 INFO - Got event: 'TabClose' on [object XULElement].
[task 2019-09-04T21:32:39.803Z] 21:32:39 INFO - Tab removed and finished closing
[task 2019-09-04T21:32:39.803Z] 21:32:39 INFO - Console message: [JavaScript Error: "TypeError: this.panelWin is null" {file: "resource://devtools/client/debugger/panel.js" line: 18}]
[task 2019-09-04T21:32:39.803Z] 21:32:39 INFO - Buffered messages finished
[task 2019-09-04T21:32:39.803Z] 21:32:39 INFO - TEST-UNEXPECTED-FAIL | devtools/client/webconsole/test/browser/browser_webconsole_telemetry_jump_to_definition.js | A promise chain failed to handle a rejection: this.panelWin is null - stack: DebuggerPanel@resource://devtools/client/debugger/panel.js:18:3
[task 2019-09-04T21:32:39.803Z] 21:32:39 INFO - build@resource://devtools/client/definitions.js:234:12
[task 2019-09-04T21:32:39.803Z] 21:32:39 INFO - onLoad@resource://devtools/client/framework/toolbox.js:2307:32
[task 2019-09-04T21:32:39.803Z] 21:32:39 INFO - Rejection date: Wed Sep 04 2019 21:32:39 GMT+0000 (Greenwich Mean Time) - false == true - JS frame :: resource://testing-common/PromiseTestUtils.jsm :: assertNoUncaughtRejections :: line 263
[task 2019-09-04T21:32:39.803Z] 21:32:39 INFO - Stack trace:
[task 2019-09-04T21:32:39.804Z] 21:32:39 INFO - resource://testing-common/PromiseTestUtils.jsm:assertNoUncaughtRejections:263
[task 2019-09-04T21:32:39.804Z] 21:32:39 INFO - chrome://mochikit/content/browser-test.js:nextTest:912
[task 2019-09-04T21:32:39.804Z] 21:32:39 INFO - chrome://mochikit/content/browser-test.js:testScope/test_finish/<:1732
[task 2019-09-04T21:32:39.804Z] 21:32:39 INFO - chrome://mochikit/content/browser-test.js:run:1647
[task 2019-09-04T21:32:39.804Z] 21:32:39 INFO - GECKO(7208) | JavaScript error: resource://testing-common/PromiseTestUtils.jsm, line 112: uncaught exception: Object
[task 2019-09-04T21:32:39.804Z] 21:32:39 INFO - Console message: [JavaScript Error: "uncaught exception: Object" {file: "resource://testing-common/PromiseTestUtils.jsm" line: 112}]
[task 2019-09-04T21:32:39.804Z] 21:32:39 INFO - GECKO(7208) | MEMORY STAT | vsize 2105077MB | vsizeMaxContiguous 65257958MB | residentFast 726MB | heapAllocated 313MB
[task 2019-09-04T21:32:39.804Z] 21:32:39 INFO - TEST-OK | devtools/client/webconsole/test/browser/browser_webconsole_telemetry_jump_to_definition.js | took 4807ms

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.