Closed Bug 1623076 Opened 5 years ago Closed 5 years ago

Perma Assertion failure: !IsExpired(), at /builds/worker/checkouts/gecko/toolkit/components/telemetry/core/TelemetryHistogram.cpp:1044 when version number gets increased to 77 on 2020-04-06

Categories

(WebExtensions :: General, defect, P1)

defect

Tracking

(firefox74 unaffected, firefox75 unaffected, firefox76+ verified)

VERIFIED FIXED
Tracking Status
firefox74 --- unaffected
firefox75 --- unaffected
firefox76 + verified

People

(Reporter: cbrindusan, Assigned: rpl)

References

Details

Central as Version Increase simulation:
https://treeherder.mozilla.org/#/jobs?repo=try&resultStatus=testfailed%2Cbusted%2Cexception&revision=b6c5aecb707dafe97258c42aff0dc001b6eeee4a&selectedJob=293494811

Failure log:
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=293494811&repo=try&lineNumber=26016

[task 2020-03-17T12:57:49.432Z] 12:57:49 INFO - TEST-START | browser/components/extensions/test/browser/browser_ext_browserAction_telemetry.js
[task 2020-03-17T12:57:49.437Z] 12:57:49 INFO - GECKO(4476) | Assertion failure: !IsExpired(), at /builds/worker/checkouts/gecko/toolkit/components/telemetry/core/TelemetryHistogram.cpp:1044

Flags: needinfo?(gwatson)
Flags: needinfo?(gwatson)
No longer regressed by: 1621390
Summary: Perma Assertion failure: !IsExpired(), at /builds/worker/checkouts/gecko/toolkit/components/telemetry/core/TelemetryHistogram.cpp:1044 when Gecko 77 merges to Beta on 2020-04-06 → Perma Assertion failure: !IsExpired(), at /builds/worker/checkouts/gecko/toolkit/components/telemetry/core/TelemetryHistogram.cpp:1044 when version number gets increased to 77 on 2020-04-06
Depends on: 1623315

I just filed Bug 1623315 (to extend or remove the probes that are expiring in Firefox 77 and triggering this test failure) and assigned it to me.

Flags: needinfo?(lgreco)
Component: Tabbed Browser → General
Product: Firefox → WebExtensions
Assignee: nobody → lgreco
Priority: -- → P1
Status: NEW → ASSIGNED

Bug 1623315 has been merged to mozilla-central a couple of days ago, and so this failure shouldn't happen in the next "version increase" simulation.

I haven't closed this issue explicitly to let it be explicitly verified by a new "version increase" simulation.

Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.