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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-rrqqQsM


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

android-webview-nexus6

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

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : document-implementation/document-implementation


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

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

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


| 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/8976994916044030032

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

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: bbf870d971d95af7ae1ee688a7ed100e3787d02b
  bad_revision : 99d25e0b826945bb98b7ff19db9ff8fb82234334

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


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : document-implementation/document-implementation

Revision             Result                  N
chromium@475300      171.115 +- 13.6072      6      good
chromium@475350      156.647 +- 7.77841      6      good
chromium@475375      148.61 +- 1.88087       6      good
chromium@475387      155.065 +- 8.73727      6      good
chromium@475389      137.873 +- 7.84482      6      bad
chromium@475390      138.941 +- 6.83246      6      bad
chromium@475393      136.013 +- 5.33582      6      bad
chromium@475399      133.169 +- 5.55048      6      bad

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

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

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


| 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/8976879747745152176

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

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: 88c8153ffb73869b07a17c3d804630e401c730fd
  bad_revision : ed4df89fed450d8f2741bba7cd2651ad28c6a779

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


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : document-implementation/document-implementation
  Change       : 21.53% | 173.299360429 -> 135.983485998

Revision             Result                  N
chromium@475300      173.299 +- 6.84727      6      good
chromium@475350      156.499 +- 8.24568      6      good
chromium@475375      144.943 +- 9.40543      6      bad
chromium@475399      135.983 +- 5.19264      6      bad

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

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

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


| 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 came back up.