Closed Bug 1784355 Opened 2 years ago Closed 2 years ago

JS debugger does no longer halt on breakpoints in content processes when running Marionette tests with --jsdebugger

Categories

(Remote Protocol :: Marionette, defect, P1)

Firefox 105
defect
Points:
1

Tracking

(firefox-esr91 unaffected, firefox-esr102 unaffected, firefox103 unaffected, firefox104 unaffected, firefox105 fixed)

RESOLVED FIXED
105 Branch
Tracking Status
firefox-esr91 --- unaffected
firefox-esr102 --- unaffected
firefox103 --- unaffected
firefox104 --- unaffected
firefox105 --- fixed

People

(Reporter: whimboo, Assigned: whimboo)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [webdriver:m4][webdriver-external])

Attachments

(1 file)

Similar to bug 1782667 which fixed it for Mochitests we need the same fix for Marionette. Otherwise the debugger won't halt on initially set breakpoints in content processes. It's a regression from bug 1782527.

The reason why Marionette is not fixed is that the harness doesn't make use of the /testing/profiles folder.

Set release status flags based on info from the regressing bug 1782527

Severity: -- → S3
Points: --- → 1
Priority: -- → P1
Whiteboard: [webdriver:m4][webdriver-external]
Pushed by hskupin@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/588a3e413225 [marionette] Start multiprocess browser toolbox when running Marionette tests with --jsdebugger. r=webdriver-reviewers,jdescottes
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 105 Branch
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: