Issue #281 - Use the most-recent version, not the most-used version for the crash dash #282
Conversation
|
Live preview can be found here: https://chutten.github.io/telemetry-dashboard/crashes/ |
|
This needs some tweaking. It needs to auto-select a day from the latest version instead of waiting for usage to increase enough to match the previous version's use, and the crash plot can probably just stop truncating on the x-axis. |
|
| return (window.parseInt(major, 10) + add) + ".0" | ||
| }; | ||
|
|
||
| var formatYYYYmmdd = function(d) { |
fbertsch
Feb 7, 2017
Collaborator
Indentation?
Indentation?
| @@ -61,6 +62,9 @@ | |||
| var gData = undefined; | |||
| var gMap = {}; | |||
|
|
|||
| // When populated, this is a map activity_date -> channel -> version | |||
| var gLatestVersions = getLatestVersions(); | |||
fbertsch
Feb 7, 2017
Collaborator
With limit=10 (at least, I think that is what is causing the problem), some options for "analyzed date" aren't showing (well, they show, but they don't update the table). Check the earliest date (2016-11-08) for an example of this. Gets a "TypeError: gMap[weekAgoDate] is undefined".
With limit=10 (at least, I think that is what is causing the problem), some options for "analyzed date" aren't showing (well, they show, but they don't update the table). Check the earliest date (2016-11-08) for an example of this. Gets a "TypeError: gMap[weekAgoDate] is undefined".
chutten
Feb 10, 2017
Author
Contributor
The first seven dates don't work as they rely on data being present a week before. I suppose I can make that safe, but it's always been that way. I've filed #284 for this.
The first seven dates don't work as they rely on data being present a week before. I suppose I can make that safe, but it's always been that way. I've filed #284 for this.
This leaves me unfortunately uncertain about what to do with them. |
They complicate debugging and add noise to the logs.
chutten
force-pushed the
chutten:gh-pages
branch
8 times, most recently
from
bd2b5e4
to
55a0ac9
|
LGTM |
The crash dash currently displays the most-used version per channel in an
effort to maximize the crash rate denominator "kuh".
This isn't terribly helpful as, once a new release lands, we cease to really
care about the stability of the old one.
So track the release schedule using https://product-details.mozilla.org and
only use data from the most recent release.
Issue #281
This change is