Closed
Bug 1780005
Opened 2 years ago
Closed 2 years ago
Add more trace logs to ProgressListener
Categories
(Remote Protocol :: Agent, task, P1)
Remote Protocol
Agent
Tracking
(firefox107 fixed)
RESOLVED
FIXED
107 Branch
Tracking | Status | |
---|---|---|
firefox107 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jdescottes)
References
Details
(Whiteboard: [webdriver:m5])
Attachments
(1 file)
See https://bugzilla.mozilla.org/show_bug.cgi?id=1779678#c3
We sometimes have intermittent failures related to navigation which are complicated to investigate because we can't tell which path was used in the ProgressListener.
We should have additional trace logs to easily understand why the ProgressListener resolved.
Assignee | ||
Updated•2 years ago
|
Points: --- → 1
Priority: -- → P3
Whiteboard: [webdriver:backlog]
Assignee | ||
Comment 1•2 years ago
|
||
Depends on D158142
Tried to cover all branches so that we know exactly why a progress listener stops or hangs.
Added a #trace private helper for readability.
Updated•2 years ago
|
Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
Updated•2 years ago
|
Priority: P3 → P1
Whiteboard: [webdriver:backlog] → [webdriver:m5]
Updated•2 years ago
|
Blocks: webdriver:m5
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/eec8be375db5 [remote] Add more trace logs to ProgressListener r=webdriver-reviewers,whimboo
Comment 3•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox107:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 107 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•