Closed
Bug 1814688
Opened 1 year ago
Closed 1 year ago
TerminatorTelemetry logspam: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsITelemetry.getHistogramById]
Categories
(Toolkit :: Async Tooling, defect)
Tracking
()
RESOLVED
FIXED
111 Branch
Tracking | Status | |
---|---|---|
firefox111 | --- | fixed |
People
(Reporter: Gijs, Assigned: barret)
Details
Attachments
(1 file)
Happens 3 times on startup on a clean profile.
Ironically the comment a few lines below: https://searchfox.org/mozilla-central/rev/11cf68787bd00edfa7ac6a0ecd07794698cdebdc/toolkit/components/terminator/TerminatorTelemetry.jsm#96-97 suggests that this should fail tests. It's not clear to me why it doesn't.
Barret, can you take a look? Would be nice to shut this up on new profiles at least.
Flags: needinfo?(brennie)
Assignee | ||
Comment 1•1 year ago
|
||
The events in question do not have associated histograms, but are included in
the JSON payload that nsTerminator writes.
The test for this functionality has been updated to reflect real conditions and
correctly fails without the fix in this patch.
Updated•1 year ago
|
Assignee: nobody → brennie
Status: NEW → ASSIGNED
Assignee | ||
Updated•1 year ago
|
Flags: needinfo?(brennie)
Pushed by brennie@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c3c671c7421a Ignore some events in TerminatorTelemetry r=chutten
Comment 3•1 year ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•