All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=690964

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmPDO6QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmNnPoAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6PfH5ggM


Bot(s) for this bug's original alert(s):

android-nexus5
android-nexus7v2
android-webview-nexus6

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988028065772835424

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : blink_perf.paint
  Metric       : large-table-repaint/large-table-repaint

Revision             Result                  N
chromium@448798      2027.68 +- 51.2115      13      good
chromium@449146      2849.44 +- 84.5518      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.paint

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8988028065772835424

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6427475518685184


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8987762772488172016

I kicked off another bisect on a different bot.

sullivan@: This bisect result is actually misleading. It is reporting "No Perf regression" but the reported result show a clear regression. Looking at the perf bot output it is in fact a build failure which has prevent a bisect to complete. So rather than reporting "No regression" this should report a "Failed" bisect.

+simonhatch can you take a look?

Hmm the bisect seems to have stopped partway through a step and the bot went purple, don't think it was a build failure but you're right, the output is totally wrong. It's supposed to say the bisect couldn't run to completion in cases like this, I'll have to dig into why it didn't.

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : blink_perf.paint
  Metric       : large-table-repaint/large-table-repaint

Revision             Result                  N
chromium@448700      1097.52 +- 27.2548      14      good
chromium@449342      1428.28 +- 36.0371      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.paint

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8987762772488172016

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6522299001339904


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.