Closed
Bug 1805471
Opened 3 years ago
Closed 3 years ago
debugging ASRouter impression handling can be painful; add logging
Categories
(Firefox :: Messaging System, task, P1)
Firefox
Messaging System
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox110 | --- | fixed |
People
(Reporter: dmosedale, Assigned: dmosedale)
Details
Attachments
(1 file)
I've got a bunch of logging in my tree from debugging multiple groups during bookmarks rollout testing; I'd like to clean it up and land it to improve future developer efficiency.
Still deciding whether I think it makes more sense to be part of the existing ASRouter logger, or if it wants its own ASRouterImpressions logger or something similar. It'll depend on what the volume looks like after I get clean up the logging.
|
Assignee | |
Updated•3 years ago
|
Iteration: --- → 109.2 - Nov 28 - Dec 9
Target Milestone: 110 Branch → ---
|
||
Updated•3 years ago
|
Iteration: 109.2 - Nov 28 - Dec 9 → 110.1 - Dec 12 - Dec 23
|
|
Assignee | |
Comment 1•3 years ago
|
||
Pushed by dmosedale@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/98b6d04fef04
add ASRouter impression debug logging, r=emcminn
|
||
Comment 3•3 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox110:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 110 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•