Closed
Bug 1813320
Opened 2 years ago
Closed 2 years ago
Console spam: Unknown category for SetEventRecordingEnabled: page_load
Categories
(Core :: Performance Engineering, defect)
Core
Performance Engineering
Tracking
()
RESOLVED
FIXED
111 Branch
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox109 | --- | unaffected |
firefox110 | --- | wontfix |
firefox111 | --- | fixed |
People
(Reporter: Gijs, Assigned: denispal)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
AFAICT bug 1799727 migrated the page_load
event telemetry to glean, but left behind: https://searchfox.org/mozilla-central/rev/4d2b1f753871ce514f9dccfc5b1b5e867f499229/dom/base/Document.cpp#1985
Telemetry::SetEventRecordingEnabled("page_load"_ns, true);
But https://phabricator.services.mozilla.com/D162311 removed that events category from Events.yaml, so now the telemetry code yells about this on each page load within the first 30s or something.
Updated•2 years ago
|
Keywords: regression
Comment 1•2 years ago
|
||
Set release status flags based on info from the regressing bug 1799727
:denispal, since you are the author of the regressor, bug 1799727, could you take a look? Also, could you set the severity field?
For more information, please visit auto_nag documentation.
status-firefox109:
--- → unaffected
status-firefox110:
--- → affected
status-firefox-esr102:
--- → unaffected
Flags: needinfo?(dpalmeiro)
Assignee | ||
Comment 2•2 years ago
|
||
Updated•2 years ago
|
Assignee: nobody → dpalmeiro
Status: NEW → ASSIGNED
Pushed by dpalmeiro@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/761172673f37
Remove Telemetry::SetEventRecordingEnabled for page_load event r=chutten
Comment 4•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
Comment 5•2 years ago
|
||
Do we want to uplift that patch to 110?
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Updated•1 year ago
|
Flags: needinfo?(dpalmeiro)
You need to log in
before you can comment on or make changes to this bug.
Description
•