Closed
Bug 1722479
Opened 3 years ago
Closed 3 years ago
browser_resources_thread_states.js fails with server targets
Categories
(DevTools :: Debugger, defect)
DevTools
Debugger
Tracking
(Fission Milestone:MVP, firefox92 fixed)
Tracking | Status | |
---|---|---|
firefox92 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
Details
(Whiteboard: dt-fission-m3-mvp)
Attachments
(1 file)
This test fails as it tries to set breakpoint only via the thread front, while it should now use thread configuration command!
It also assume the thread front would stay the same over reload, while it won't be the case with server targets...
We might scan all the test to migrate to thread configuration command everywhere...
Assignee | ||
Comment 1•3 years ago
|
||
We should now set breakpoints with thread configuration command,
especially when any navigation/reload happen.
Also, we should acknowledge that the threadFront may change on each navigation/reload.
Pushed by apoirot@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/84d67c4d9666 [devtools] Fix browser_resources_thread_states.js with server targets. r=bomsy
Comment 3•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox92:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 92 Branch
Updated•3 years ago
|
Fission Milestone: --- → MVP
Whiteboard: dt-fission-m3-mvp
You need to log in
before you can comment on or make changes to this bug.
Description
•