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

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


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

android-nexus6

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

=== 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.shadow_dom
  Metric       : v1-slot-append/v1-slot-append

Revision                           Result                  N
chromium@455707                    386.2 +- 4.96264        6      good
chromium@455714                    381.039 +- 6.1109       6      good
chromium@455718                    393.012 +- 8.09299      6      good
chromium@455719                    395.011 +- 7.15349      6      good
chromium@455719,v8@fbffc377e3      353.266 +- 3.51493      6      bad
chromium@455720                    353.834 +- 4.50765      6      bad
chromium@455721                    344.355 +- 3.75538      6      bad
chromium@455734                    349.405 +- 4.85316      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.shadow_dom

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

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


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