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

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


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

android-nexus6

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

=== 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: b89328b48bc2ae3366c506cb32adb996e0493685
  bad_revision : 2c4f825e2457eaaa9eed63daddf83822da88e864

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


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : dom-attribute-on-prototoype/dom-attribute-on-prototoype

Revision             Result                   N
chromium@472979      24.9023 +- 1.06135       5      good
chromium@473024      23.7633 +- 0.646893      6      bad
chromium@473068      23.2895 +- 1.17743       6      bad
chromium@473157      21.7221 +- 0.766264      6      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.bindings

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

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


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

=== 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: 6739a6938d0245598eb5458421da3aa1bd27b011
  bad_revision : b72ebe3be808b64ca15ebff036511450b4a8fcff

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


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : dom-attribute-on-prototoype/dom-attribute-on-prototoype

Revision             Result                   N
chromium@472979      24.8355 +- 0.387454      7      good
chromium@472991      25.3514 +- 1.0112        6      good
chromium@472997      25.1065 +- 1.22696       6      good
chromium@472999      24.1055 +- 0.585031      6      bad
chromium@473000      24.1014 +- 0.384805      6      bad
chromium@473002      24.1177 +- 0.748443      5      bad
chromium@473024      23.6129 +- 0.949716      6      bad
chromium@473068      22.9587 +- 1.36263       6      bad
chromium@473157      21.6408 +- 0.664627      6      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.bindings

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

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


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

=== 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: 55849b167c16bb7f87b5c747b02d27f531bc4086
  bad_revision : 7bbea08f669df4f6dee69cd7b0629959ca372a37

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


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : dom-attribute-on-prototoype/dom-attribute-on-prototoype

Revision                           Result                   N
chromium@472800                    13.8929 +- 0.595567      6      good
chromium@473000                    13.5577 +- 0.985804      6      good
chromium@473100                    13.9594 +- 0.723981      6      good
chromium@473113                    13.4237 +- 1.09589       6      good
chromium@473119                    13.7646 +- 0.891621      6      good
chromium@473120                    13.2618 +- 0.905348      6      good
chromium@473120,v8@55849b167c      13.2203 +- 0.61012       6      good
chromium@473120,v8@7bbea08f66      11.5256 +- 0.746909      6      bad
chromium@473121                    11.6175 +- 0.318416      6      bad
chromium@473122                    11.3656 +- 0.549231      6      bad
chromium@473125                    11.787 +- 0.434932       6      bad
chromium@473150                    12.1428 +- 0.595495      6      bad
chromium@473200                    12.2514 +- 0.615983      6      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.bindings

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

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


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

=== 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: 55849b167c16bb7f87b5c747b02d27f531bc4086
  bad_revision : 7bbea08f669df4f6dee69cd7b0629959ca372a37

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


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : dom-attribute-on-prototoype/dom-attribute-on-prototoype

Revision                           Result                   N
chromium@472800                    14.0155 +- 1.30592       9      good
chromium@473000                    13.7023 +- 1.22915       9      good
chromium@473100                    14.135 +- 0.763209       6      good
chromium@473113                    13.2033 +- 0.649879      6      good
chromium@473119                    13.9391 +- 0.468264      6      good
chromium@473120                    13.1949 +- 0.574325      6      good
chromium@473120,v8@55849b167c      13.1842 +- 0.508825      6      good
chromium@473120,v8@7bbea08f66      11.7975 +- 0.571157      6      bad
chromium@473121                    11.6947 +- 0.260114      6      bad
chromium@473122                    11.8254 +- 0.60413       6      bad
chromium@473125                    11.3909 +- 0.966015      6      bad
chromium@473150                    12.0501 +- 0.300789      6      bad
chromium@473200                    12.3284 +- 1.96164       9      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.bindings

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

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


| 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.