reject crash reports from unsupported product versions
Categories
(Socorro :: Antenna, task, P3)
Tracking
(Not tracked)
People
(Reporter: willkg, Unassigned)
Details
The collector has a match_old_buildid matcher which looks at the BuildID value and rejects anything with a build id > 2 years. With this match, we still get into the situation where we did a build recently, but now the version is no longer supported.
For example, at this time (September 19th, 2022) 78 ESR is no longer supported, but the last build id is dated September 21, 2021. It'll take a year until those crash reports start getting rejected even though we no longer support 78 ESR.
We got 20k crash reports for 78 ESR in the last 7 days.
We should probably have a rule that rejects unsupported versions.
I think we'd have to manually maintain this. It's possible we could infer the supported releases from the product details information:
https://product-details.mozilla.org/1.0/firefox_versions.json
|
Reporter | |
Comment 1•3 years ago
|
||
jcristau says:
78 is where we parked osx < 10.12 so lots of macos crashes in that list
We wouldn't be able infer that from the product details data. So maybe doing this automatically isn't a great idea.
|
||
Comment 2•3 years ago
|
||
Given that we know in advance for how long we're going to support a given version we might hard-code that in Firefox instead.
Description
•