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

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


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

android-nexus5X

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

That bot is currently running crazy. You can ignore it.

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : speedometer-ignition
  Metric       : Total/Total

Revision             Result                  N
chromium@451825      29095.4 +- 15842.9      21      good
chromium@452845      29598.8 +- 13654.0      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-ignition

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

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


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