Closed Bug 1374187 Opened 3 years ago Closed 1 year ago

Intermittent devtools/client/debugger/new/test/mochitest/browser_dbg-chrome-debugging.js | A promise chain failed to handle a rejection: Invalid process ID: 0 - rejection date: Sun Jun 18 2017 19:54:25 GMT+0000 (UTC) - stack: onFailure@resource://gre/modu

Categories

(DevTools :: Debugger, defect)

Product:
DevTools
Component:
Debugger
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox56 fixed)

Status:
RESOLVED FIXED
Milestone:
Firefox 56
Tracking Flags:
Tracking Status
firefox56 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: jmaher)

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell disabled])

Attachments

(1 file)

disable test on debug
1.05 KB, patch
KWierso
: review+
Details | Diff | Splinter Review 
this started on June 18th on debug/asan, heavily on linux64-asan.

here is a log for linux64-asan:
https://treeherder.mozilla.org/logviewer.html#?repo=try&job_id=109237058

and data from the log:
[task 2017-06-22T15:23:35.212650Z] 15:23:35     INFO - TEST-START | devtools/client/debugger/new/test/mochitest/browser_dbg-chrome-debugging.js
[task 2017-06-22T15:23:36.550652Z] 15:23:36     INFO - GECKO(1107) | JavaScript warning: resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/builtin-modules.js, line 152: DebuggeeWouldRun: debuggee `resource://gre/modules/commonjs/toolkit/loader.js:864' would run
[task 2017-06-22T15:23:36.667683Z] 15:23:36     INFO - GECKO(1107) | JavaScript warning: resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/builtin-modules.js, line 152: DebuggeeWouldRun: debuggee `resource://gre/modules/commonjs/toolkit/loader.js:864' would run
[task 2017-06-22T15:23:38.104603Z] 15:23:38     INFO - TEST-INFO | started process screentopng
[task 2017-06-22T15:23:40.179964Z] 15:23:40     INFO - TEST-INFO | screentopng: exit 0
[task 2017-06-22T15:23:40.190449Z] 15:23:40     INFO - Buffered messages logged at 15:23:35
[task 2017-06-22T15:23:40.192275Z] 15:23:40     INFO - Entering test bound 
[task 2017-06-22T15:23:40.194488Z] 15:23:40     INFO - TEST-PASS | devtools/client/debugger/new/test/mochitest/browser_dbg-chrome-debugging.js | Root actor should identify itself as a browser. - 
[task 2017-06-22T15:23:40.198993Z] 15:23:40     INFO - Buffered messages logged at 15:23:37
[task 2017-06-22T15:23:40.201539Z] 15:23:40     INFO - Console message: [JavaScript Warning: "DebuggeeWouldRun: debuggee `resource://gre/modules/commonjs/toolkit/loader.js:864' would run" {file: "resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/builtin-modules.js" line: 152}]
[task 2017-06-22T15:23:40.203917Z] 15:23:40     INFO - TEST-PASS | devtools/client/debugger/new/test/mochitest/browser_dbg-chrome-debugging.js | Received a new chrome source: chrome://browser/content/tabbrowser.xml - 
[task 2017-06-22T15:23:40.214499Z] 15:23:40     INFO - TEST-PASS | devtools/client/debugger/new/test/mochitest/browser_dbg-chrome-debugging.js | Received a new chrome global. - 
[task 2017-06-22T15:23:40.219585Z] 15:23:40     INFO - Console message: [JavaScript Warning: "DebuggeeWouldRun: debuggee `resource://gre/modules/commonjs/toolkit/loader.js:864' would run" {file: "resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/builtin-modules.js" line: 152}]
[task 2017-06-22T15:23:40.224616Z] 15:23:40     INFO - Buffered messages finished
[task 2017-06-22T15:23:40.236850Z] 15:23:40     INFO - TEST-UNEXPECTED-FAIL | devtools/client/debugger/new/test/mochitest/browser_dbg-chrome-debugging.js | A promise chain failed to handle a rejection: Invalid process ID: 0 - rejection date: Thu Jun 22 2017 15:23:34 GMT+0000 (UTC) - stack: onFailure@resource://gre/modules/subprocess/subprocess_common.jsm:121:5
[task 2017-06-22T15:23:40.240325Z] 15:23:40     INFO - onmessage@resource://gre/modules/subprocess/subprocess_common.jsm:107:9
[task 2017-06-22T15:23:40.242219Z] 15:23:40     INFO -  - false == true - JS frame :: resource://testing-common/PromiseTestUtils.jsm :: assertNoUncaughtRejections :: line 257
[task 2017-06-22T15:23:40.246240Z] 15:23:40     INFO - Stack trace:
[task 2017-06-22T15:23:40.247801Z] 15:23:40     INFO -     resource://testing-common/PromiseTestUtils.jsm:assertNoUncaughtRejections:257
[task 2017-06-22T15:23:40.249385Z] 15:23:40     INFO -     chrome://mochikit/content/browser-test.js:Tester_execTest/<:801
[task 2017-06-22T15:23:40.250806Z] 15:23:40     INFO -     Tester_execTest@chrome://mochikit/content/browser-test.js:774:9
[task 2017-06-22T15:23:40.253586Z] 15:23:40     INFO -     Tester.prototype.nextTest</<@chrome://mochikit/content/browser-test.js:686:7
[task 2017-06-22T15:23:40.255230Z] 15:23:40     INFO -     SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:795:59
[task 2017-06-22T15:23:40.262210Z] 15:23:40     INFO - Leaving test bound 
[task 2017-06-22T15:23:40.266359Z] 15:23:40     INFO - Removing tab.
[task 2017-06-22T15:23:40.268308Z] 15:23:40     INFO - Waiting for event: 'TabClose' on [object XULElement].
[task 2017-06-22T15:23:40.271365Z] 15:23:40     INFO - Got event: 'TabClose' on [object XULElement].
[task 2017-06-22T15:23:40.279675Z] 15:23:40     INFO - Tab removed and finished closing
[task 2017-06-22T15:23:40.281808Z] 15:23:40     INFO - GECKO(1107) | MEMORY STAT | vsize 20974067MB | residentFast 885MB
[task 201
7-06-22T15:23:40.287025Z] 15:23:40     INFO - TEST-OK | devtools/client/debugger/new/test/mochitest/browser_dbg-chrome-debugging.js | took 3498ms


:jlast, this is trending fast, 38 failures in the last week and a higher rate in recent days- could you get this resolved in the next 2 weeks or help find someone to resolve this?
Flags: needinfo?(jlaster)
Whiteboard: [stockwell needswork]
I believe that this test spiked for the same reason that the browser toolbox test spiked two weeks ago. We have a patch [1] that should land this week, which will help address them both.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1376135
Flags: needinfo?(jlaster)
(In reply to Jason Laster [:jlast] from comment #6)
> I believe that this test spiked for the same reason that the browser toolbox
> test spiked two weeks ago. We have a patch [1] that should land this week,
> which will help address them both.
> 
> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1376135

That seemed to help, but failures continue...I expect perhaps about 30/week now.
We had a new release yesterday that added further perf wins. Lets see if the rate goes down a bit.
:jlast will this test be ok to disable and be deprecated in 2 weeks when 56 goes to beta?
Flags: needinfo?(jlaster)
there are a few e10s failures, but debug is there for all failures.
Attachment #8889648 - Flags: review?(wkocher)
Pushed by jmaher@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/ae95f5d9d6a3
Intermittent devtools/client/debugger/new/test/mochitest/browser_dbg-chrome-debugging.js. skip on deug. r=KWierso
https://hg.mozilla.org/mozilla-central/rev/ae95f5d9d6a3
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox56: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 56
Status: RESOLVED → REOPENED
Keywords: leave-open
Resolution: FIXED → ---
Whiteboard: [stockwell needswork] → [stockwell disabled]
Flags: needinfo?(jlaster)
Product: Firefox → DevTools
Status: REOPENED → RESOLVED
Closed: 3 years ago → 1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.