1644457 - browser/components/attribution/test/browser/browser_AttributionCode_telemetry.js will fail because BROWSER_ATTRIBUTION_ERRORS probe expires when Gecko version gets increased to 80 on 2020-06-29

Status: RESOLVED DUPLICATE of bug 1645078

(Firefox :: Messaging System, defect)

Description

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

version increase simulation: https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel%2Crunnable&revision=c117756d889cf371cfba39a084ffe1cd56d0ad8f&selectedTaskRun=VbqwutQqTliarGBLbbTmcg-0

Log: https://treeherder.mozilla.org/logviewer.html#?job_id=305624977&repo=try

TEST-UNEXPECTED-FAIL | browser/components/attribution/test/browser/browser_AttributionCode_telemetry.js | Uncaught exception - at resource://testing-common/TelemetryTestUtils.jsm:288 - TypeError: can't access property "values", snapshot is undefined

Comment 1

[Andrei Oprea [:andreio]]

Have we used this telemetry probe data so far? Was it useful to just get an idea of what the success / failure rates are like or should we keep collecting the data beyond Firefox 80?

Comment 2

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

(In reply to Andrei Oprea [:andreio] from comment #1)

beyond Firefox 80?

beyond Firefox 79.

Comment 3

[Su-Young Hong]

Hey,

It's fine to remove this telemetry. It's not supporting anything specific right now, and the original concern that landed it was addressed.