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

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


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

android-nexus5X
android-nexus6

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : speedometer
  Metric       : AngularJS-TodoMVC/AngularJS-TodoMVC

Revision             Result                  N
chromium@460720      5346.51 +- 1515.21      21      good
chromium@460769      5404.16 +- 1212.27      21      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 speedometer

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

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


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