Closed
Bug 1256734
Opened 9 years ago
Closed 5 years ago
Investigate large number of CHK_DOWNLOAD_UPDATE pings
Categories
(Toolkit :: Application Update, defect, P3)
Toolkit
Application Update
Tracking
()
RESOLVED
DUPLICATE
of bug 1560563
People
(Reporter: spohl, Unassigned)
References
Details
The update orphaning dashboard[1] shows that over 8% of users who are more than two version out-of-date are reporting a value of CHK_ADDON_NO_INCOMPAT for UPDATE_CHECK_CODE_NOTIFY. This value should only be reported when a Firefox install first discovers that an update is available. We should verify that this is the case and understand if there is truly such a large number of users who are only just discovering an update when they're already two versions behind.
[1] https://telemetry.mozilla.org/update-orphaning/
Comment 1•7 years ago
|
||
Is this still valid Stephen? Looking at the current report, I didn't find your 8% chunk.
Flags: needinfo?(spohl.mozilla.bugs)
Reporter | ||
Comment 2•7 years ago
|
||
The update orphaning dashboard is now handled by mhowell. Forwarding n-i.
Flags: needinfo?(spohl.mozilla.bugs) → needinfo?(mhowell)
Comment 3•7 years ago
|
||
First, I'm changing the summary because we got rid of the addon compatibility check back in bug 1262880 and this check code was renamed.
We are still getting quite a few of these pings though, it's actually 13.8% for last week according to the dashboard.
This code means that we found an update and started trying to download it, but that download is still in flight, it hasn't either succeeded or failed yet. These clients should therefore be making it into the download code portion of the dashboard, in the "no ping" category. I'm not sure there's anything really actionable with just this check code.
Flags: needinfo?(mhowell)
Summary: Investigate large number of CHK_ADDON_NO_INCOMPAT pings → Investigate large number of CHK_DOWNLOAD_UPDATE pings
Updated•7 years ago
|
Priority: -- → P3
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•