Closed Bug 1462391 Opened 6 years ago Closed 6 years ago

Show individual builds in telemetry evolution

Categories

(Data Platform and Tools :: General, defect)

Product:
Data Platform and Tools
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1347564

People

(Reporter: mccr8, Unassigned)

References

Details

The regression that ended up being bug 1449033 was caused by bug 1432794, which was first part of the 20180130223236 build:
  https://hg.mozilla.org/mozilla-central/rev/1b4d5be72031

The regression did distinctly show up in telemetry evolution:
  https://mzl.la/2Is0mys

However, on telemetry it looks like it was first introduced on a January 31 build, not a January 30 build. I did see this regression ahead of time and tried to figure out what was causing it based on the changesets that landed in the January 31 build, but as it turns out, that would have never worked.

As it happens, in this particular case, I think that even if I had had the correct regression range I would not have been able to figure out what was causing the regression, but in other cases having the right range would help.
Oops, I forgot that I filed this last week.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Product: Webtools → Data Platform and Tools
Component: Telemetry Dashboards (TMO) → General
You need to log in before you can comment on or make changes to this bug.