Remove or update metrics expiring in Firefox 134: gfx.tmp_writable before Gecko version gets increased to 134 on 2024-10-28
Categories
(Core :: Audio/Video: GMP, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox131 | --- | unaffected |
firefox132 | --- | unaffected |
firefox133 | --- | unaffected |
firefox134 | + | fixed |
People
(Reporter: aryx, Assigned: aosmond)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
The probe gfx.tmp_writable
got added in bug 1923741 and will expire with the first version increase which will cause the fog python suite to fail toolkit/components/glean/tests/pytest/test_no_expired_metrics.py::test_no_metrics_expired
.
Because it hasn't shipped to release yet, the two likely options are to extend it (useful if Firefox were to apply mitigations against the issue in future releases) or have the probe removed directly from mozilla-central after the version increase.
Comment 1•9 months ago
|
||
The bug is marked as tracked for firefox133 (nightly). We have limited time to fix this, the soft freeze is in a day. However, the bug still isn't assigned.
:jimm, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Comment 2•9 months ago
|
||
Merge day is on Monday 2024-10-28, reaching out on slack to get this investigated.
Comment 3•9 months ago
|
||
Follow-up, the plan is to remove this after the Fx134 version bump.
It will ride the train to beta with Fx133
Updated•9 months ago
|
Assignee | ||
Comment 4•9 months ago
|
||
Updated•9 months ago
|
Assignee | ||
Updated•9 months ago
|
Comment 6•9 months ago
|
||
bugherder |
Updated•9 months ago
|
Description
•