Remove or update probes expiring in Firefox 132: media.audio_process_per_codec_name before Gecko version gets increased to 132 on 2024-09-02
Categories
(Core :: Audio/Video, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox129 | --- | unaffected |
firefox130 | --- | unaffected |
firefox131 | + | fixed |
People
(Reporter: telemetry-probes, Assigned: gerard-majax)
References
Details
(Whiteboard: [probe-expiry-alert])
Attachments
(1 file)
The following Firefox probes will expire in the next major Firefox nightly release: version 132 [1].
media.audio_process_per_codec_name
What to do about this:
- If one, some, or all of the metrics are no longer needed, please remove them from their definitions files (Histograms.json, Scalars.yaml, Events.yaml).
- If one, some, or all of the metrics are still required, please submit a patch to extend their expiry.
If you have any problems, please ask for help on the #data-help Slack channel or the #telemetry Matrix room at https://chat.mozilla.org/#/room/#telemetry:mozilla.org. We'll give you a hand.
Your Friendly, Neighborhood Telemetry Team
[1] https://wiki.mozilla.org/Release_Management/Calendar
This is an automated message sent from probe-scraper. See https://github.com/mozilla/probe-scraper for details.
Comment 1•2 months ago
|
||
Tracking because e.g. ipc/glue/test/browser/browser_audio_telemetry_content.js checks for this.
Comment 2•2 months ago
|
||
The bug is marked as tracked for firefox131 (nightly). However, the bug still isn't assigned.
:jimm, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Comment 3•1 month ago
|
||
We filed this for the Utility AudioDecoder work, which from my point of view is done and we would not need it anymore. Do you think we should renew ?
Comment 4•1 month ago
|
||
I'm good to remove that if we don't need that for any future analysis.
Comment 6•1 month ago
|
||
Reminder: The change must land this week before central merges to beta next Monday.
Assignee | ||
Comment 7•1 month ago
|
||
(In reply to Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout) from comment #6)
Reminder: The change must land this week before central merges to beta next Monday.
I'm lost here: current nightly is 131, so we want to change that when we move to 132, no?
Comment 8•1 month ago
|
||
The test will start to fail once the version has been increased to 132 next Monday, and the test must not fail permanently.
If the code is not needed anymore independent of the version, it should be removed if this week. Else the test needs to be disabled next Monday. If the probe should be kept in 131 but removed from 132, please provide a patch and it will be landed next Monday directly after the version got increased to 132.
Assignee | ||
Comment 9•1 month ago
|
||
Comment 10•1 month ago
|
||
Comment 11•1 month ago
|
||
bugherder |
Description
•