875851 - Create improved end-to-end report

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect)

Description

[John Hopkins (:jhopkins)]

The gofaster dashboard reports average end-to-end times for mozilla-central.

We'd like to also report on the 'try' and mozilla-inbound branches, plus have the following details graphed: min, max, average, and standard deviation (similar to a high/low/close stock report).  Outliers beyond 95th percentile can be ignored.

Comment 1

[John Hopkins (:jhopkins)]

Attachment: wip end-to-end query

First pass at pulling end-to-end data out of the scheduler db.  Does not exclude outliers.

Comment 2

[John Hopkins (:jhopkins)]

catlee and I agreed on the following specific goals:

- add the following enhancements to the gofaster graphs:
 - enhanced gantt chart showing builder times across a time range
  - elapsed times grouped into buckets on a stacked graph
 - separate page showing a single builder over time
 - add try and inbound data and allow user to select which to use
  - start with inbound, since try is a very different thing and wait times for try are the most important statistic.  "Where time is spent during a build" can be gleaned from non-try.
 - add min/max/stddev (if not stddev then some indication of the distribution) to end-to-end times (average) graph

Tasks, in priority order:

1) initial gantt chart UI that covers a range of time
2) average end-to-end time changes
3) drilling down into gantt chart
4) add other branch datasets.  switch gofaster to mozilla-inbound for starters if that is easiest.

Comment 3

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Found in triage.

Comment 4

[John Hopkins (:jhopkins)]

Wrote initial proof-of-concept but not actively working on this now.