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

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


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

android-nexus6

=== Auto-CCing suspected CL author chrisha@chromium.org ===

Hi chrisha@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Roll Syzygy binaries to 0.8.19.0.
Author  : chrisha
Commit description:
  
This includes experimental Crashpad integration.

BUG= 565768 

Review-Url: https://codereview.chromium.org/2060913002
Cr-Commit-Position: refs/heads/master@{#399470}
Commit  : 6d674d63d4831b4f7ed41fe0146f776509e7116f
Date    : Mon Jun 13 17:04:46 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@399463  5621.11  48.9902  8  good
chromium@399469  5620.3   45.0322  5  good
chromium@399470  5752.28  25.8945  5  bad    <--
chromium@399471  5708.19  23.9581  5  bad
chromium@399472  5729.61  32.796   5  bad
chromium@399474  5700.88  45.624   8  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 619847

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: jQuery-TodoMVC/jQuery-TodoMVC
Relative Change: 1.40%
Score: 99.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2235
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009895241098599984


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5850584846958592

| 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 Tests>AutoBisect.  Thank you!

Is it possible the bisect is flaky? The CL in question was a roll of an external toolchain that is only used for official SyzyAsan release builds on the Windows platform. I don't see how it could possibly be causing problems on Android.

Yes, I suppose the benchmark could be flaky.  If you're confident this CL is innocent, I'm changing this to Won't Fix.