Closed Bug 1603087 Opened 4 years ago Closed 4 years ago

Permafailing browser_application_panel_debug-service-worker.js | Test timed out - when Gecko 73 merges to beta on 2020-01-06

Categories

(DevTools :: Application Panel, defect, P1)

defect

Tracking

(firefox-esr68 unaffected, firefox71 unaffected, firefox72 unaffected, firefox73+ verified)

VERIFIED FIXED
Firefox 73
Tracking Status
firefox-esr68 --- unaffected
firefox71 --- unaffected
firefox72 --- unaffected
firefox73 + verified

People

(Reporter: nataliaCs, Assigned: ladybenko)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression, Whiteboard: [m1.1-mvp])

Attachments

(1 file)

[Tracking Requested - why for this release]:
Central as Beta: https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&revision=02a9e0de678e77078824486d5ffaca129814e41a&searchStr=devtools&selectedJob=280659198

Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=280659198&repo=try&lineNumber=966

[task 2019-12-11T11:36:05.513Z] 11:36:05 INFO - Click on the debug button and wait for debugger to be ready
[task 2019-12-11T11:36:05.513Z] 11:36:05 INFO - Waiting for state change: loaded source
[task 2019-12-11T11:36:05.514Z] 11:36:05 INFO - Console message: [JavaScript Error: "TypeError: workerTargetFront.threadFront is null" {file: "resource://devtools/client/debugger/panel.js" line: 181}]
[task 2019-12-11T11:36:05.514Z] 11:36:05 INFO - Buffered messages finished
[task 2019-12-11T11:36:05.514Z] 11:36:05 INFO - TEST-UNEXPECTED-FAIL | devtools/client/application/test/browser/browser_application_panel_debug-service-worker.js | Test timed out -
[task 2019-12-11T11:36:05.514Z] 11:36:05 INFO - Removing tab.
[task 2019-12-11T11:36:05.514Z] 11:36:05 INFO - Waiting for event: 'TabClose' on [object XULElement].
[task 2019-12-11T11:36:05.523Z] 11:36:05 INFO - Got event: 'TabClose' on [object XULElement].
[task 2019-12-11T11:36:05.543Z] 11:36:05 INFO - Tab removed and finished closing
[task 2019-12-11T11:36:05.545Z] 11:36:05 INFO - TEST-PASS | devtools/client/application/test/browser/browser_application_panel_debug-service-worker.js | The main process DebuggerServer has no pending connection when the test ends -
[task 2019-12-11T11:36:05.569Z] 11:36:05 INFO - Not taking screenshot here: see the one that was previously logged
[task 2019-12-11T11:36:05.569Z] 11:36:05 INFO - TEST-UNEXPECTED-FAIL | devtools/client/application/test/browser/browser_application_panel_debug-service-worker.js | A promise chain failed to handle a rejection: workerTargetFront.threadFront is null - stack: selectWorker@resource://devtools/client/debugger/panel.js:181:22
[task 2019-12-11T11:36:05.569Z] 11:36:05 INFO - openWorkerInDebugger@resource://devtools/client/application/src/modules/application-services.js:36:19
[task 2019-12-11T11:36:05.569Z] 11:36:05 INFO - Rejection date: Wed Dec 11 2019 11:35:21 GMT+0000 (Greenwich Mean Time) - false == true - JS frame :: resource://testing-common/PromiseTestUtils.jsm :: assertNoUncaughtRejections :: line 265
[task 2019-12-11T11:36:05.569Z] 11:36:05 INFO - Stack trace:
[task 2019-12-11T11:36:05.569Z] 11:36:05 INFO - resource://testing-common/PromiseTestUtils.jsm:assertNoUncaughtRejections:265
[task 2019-12-11T11:36:05.569Z] 11:36:05 INFO - chrome://mochikit/content/browser-test.js:nextTest:624
[task 2019-12-11T11:36:05.569Z] 11:36:05 INFO - GECKO(1679) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2019-12-11T11:36:05.569Z] 11:36:05 INFO - GECKO(1679) | MEMORY STAT | vsize 7638MB | residentFast 366MB | heapAllocated 132MB
[task 2019-12-11T11:36:05.569Z] 11:36:05 INFO - TEST-OK | devtools/client/application/test/browser/browser_application_panel_debug-service-worker.js | took 45384ms

entering test: TEST-START | devtools/client/application/test/browser/browser_application_panel_debug-service-worker.js

Belén could you please take a look at this? Thank you.

Flags: needinfo?(balbeza)
Assignee: nobody → balbeza
Status: NEW → ASSIGNED
Priority: -- → P1
Whiteboard: [m1.1-mvp]

Since parent_intercept requires to be set from the beginning, either we disable the test when it's not the case, or we force the pref to be flipped for this test… I chose the former, but happy to do the latter if it's preferable.

Flags: needinfo?(balbeza)
Flags: needinfo?(balbeza)
Pushed by balbeza@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bde70ac1c453
Disable test when parent_intercept is false r=jdescottes

Hi Razvan, thanks for taking a look! I just sent the patch to autoland

Flags: needinfo?(balbeza)
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 73
Has Regression Range: --- → yes
Keywords: regression
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: