Closed
Bug 1795653
Opened 2 years ago
Closed 2 years ago
Add trace logs when ProgressListener starts/stops
Categories
(Remote Protocol :: Agent, task, P1)
Remote Protocol
Agent
Tracking
(firefox108 fixed)
RESOLVED
FIXED
108 Branch
| Tracking | Status | |
|---|---|---|
| firefox108 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jdescottes)
References
Details
(Whiteboard: [webdriver:m5])
Attachments
(1 file)
In Bug 1780005, we added trace logs for most error/exit conditions in the ProgressListener. But it would also be helpful to have trace logs when the Progress Listener starts and stops. Otherwise, you might sometimes see an orphaned log, and it's hard to tell if this is for a new progress listener instance, or if it relates to something which happened earlier in the test (especially for the unload timer ones).
I propose de add another set of trace logs. This is a critical part of our codebase and we need to understand clearly what happened in terms of navigation when looking at a failure log from try.
|
Assignee | |
Comment 1•2 years ago
|
||
|
||
Updated•2 years ago
|
Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/219f3143688a [remote] Add trace logs when ProgressListener starts/stops r=webdriver-reviewers,whimboo
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox108:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
|
||
Updated•2 years ago
|
Points: --- → 1
Priority: -- → P1
Whiteboard: [webdriver:m5]
You need to log in
before you can comment on or make changes to this bug.
Description
•