Dashboard - Support build failures in bisect output.

Dashboard - Support build failures in bisect output.

Previously the recipe filtered the json data and the dashboard just outputted whatever was there. With this CL the dashboard will selectively print out build failures from the revision data depending on whether they're in the culprit range.

Note: Not much of the output should change at first, only thing that should change is when we push the json data changes to prod you should see this for build failures:

===== TESTED REVISIONS =====
Revision  Mean  Std Dev  N    Good?
100       100   0        10   good
102       100   0        10   good
103       ---   ---      ---  build failure
104       ---   ---      ---  build failure
105       200   0        10   bad
106       200   0        10   bad


Or in the case of lots and lots of failures:
===== TESTED REVISIONS =====
Revision  Mean  Std Dev  N    Good?
100       100   0        10   good
102       100   0        10   good
103       ---   ---      ---  build failure
---       ---   ---      ---  too many build failures to list
114       ---   ---      ---  build failure
115       200   0        10   bad
116       200   0        10   bad


BUG=chromium:668540, chromium:665439
Review-Url: https://codereview.chromium.org/2588143002
Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/28346a164856545190e1f6c3b76ac6b1c354c82f

[shatch, 2016-12-19 20:53:37]

Patchset #1 (id:1) has been deleted

[shatch, 2016-12-19 21:02:13]

Description was changed from

==========
Dashboard - Rework bisect report.

BUG=chromium:668540, chromium:665439
==========

to

==========
Dashboard - Support build failures in bisect output.

Previously the recipe filtered the json data and the dashboard just outputted
whatever was there. With this CL the dashboard will selectively print out build
failures from the revision data depending on whether they're in the culprit
range.

Note: Not much of the output should change at first, only thing that should
change is when we push the json data changes to prod you should see this for
build failures:

===== TESTED REVISIONS =====
Revision  Mean  Std Dev  N    Good?
100       100   0        10   good
102       100   0        10   good
103       ---   ---      ---  build failure
104       ---   ---      ---  build failure
105       200   0        10   bad
106       200   0        10   bad


Or in the case of lots and lots of failures:
===== TESTED REVISIONS =====
Revision  Mean  Std Dev  N    Good?
100       100   0        10   good
102       100   0        10   good
103       ---   ---      ---  build failure
---       ---   ---      ---  too many build failures to list
114       ---   ---      ---  build failure
115       200   0        10   bad
116       200   0        10   bad


BUG=chromium:668540, chromium:665439
==========

[shatch, 2016-12-19 21:02:28]

simonhatch@chromium.org changed reviewers:
+ sullivan@chromium.org

[sullivan, 2016-12-19 22:00:23]

lgtm

This is going to make things much easier to read!

[shatch, 2016-12-20 18:14:18]

The CQ bit was checked by simonhatch@chromium.org

[commit-bot: I haz the power, 2016-12-20 18:14:22]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-20 18:32:44]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1482257658219990,
"parent_rev": "70f42a7c55ca69cdeb9aa6ec7e40ff3f155040b9", "commit_rev":
"28346a164856545190e1f6c3b76ac6b1c354c82f"}

[commit-bot: I haz the power, 2016-12-20 18:32:50]

Description was changed from

==========
Dashboard - Support build failures in bisect output.

Previously the recipe filtered the json data and the dashboard just outputted
whatever was there. With this CL the dashboard will selectively print out build
failures from the revision data depending on whether they're in the culprit
range.

Note: Not much of the output should change at first, only thing that should
change is when we push the json data changes to prod you should see this for
build failures:

===== TESTED REVISIONS =====
Revision  Mean  Std Dev  N    Good?
100       100   0        10   good
102       100   0        10   good
103       ---   ---      ---  build failure
104       ---   ---      ---  build failure
105       200   0        10   bad
106       200   0        10   bad


Or in the case of lots and lots of failures:
===== TESTED REVISIONS =====
Revision  Mean  Std Dev  N    Good?
100       100   0        10   good
102       100   0        10   good
103       ---   ---      ---  build failure
---       ---   ---      ---  too many build failures to list
114       ---   ---      ---  build failure
115       200   0        10   bad
116       200   0        10   bad


BUG=chromium:668540, chromium:665439
==========

to

==========
Dashboard - Support build failures in bisect output.

Previously the recipe filtered the json data and the dashboard just outputted
whatever was there. With this CL the dashboard will selectively print out build
failures from the revision data depending on whether they're in the culprit
range.

Note: Not much of the output should change at first, only thing that should
change is when we push the json data changes to prod you should see this for
build failures:

===== TESTED REVISIONS =====
Revision  Mean  Std Dev  N    Good?
100       100   0        10   good
102       100   0        10   good
103       ---   ---      ---  build failure
104       ---   ---      ---  build failure
105       200   0        10   bad
106       200   0        10   bad


Or in the case of lots and lots of failures:
===== TESTED REVISIONS =====
Revision  Mean  Std Dev  N    Good?
100       100   0        10   good
102       100   0        10   good
103       ---   ---      ---  build failure
---       ---   ---      ---  too many build failures to list
114       ---   ---      ---  build failure
115       200   0        10   bad
116       200   0        10   bad


BUG=chromium:668540, chromium:665439

Review-Url: https://codereview.chromium.org/2588143002
Committed:
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...
==========

[commit-bot: I haz the power, 2016-12-20 18:32:51]

Committed patchset #2 (id:40001) as
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...