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

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


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

android-nexus7v2
chromium-rel-win7-x64-dual

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

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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : speedometer
  Metric       : FlightJS-TodoMVC/FlightJS-TodoMVC

Revision             Result                 N
chromium@452777      2524.5 +- 337.417      21      good
chromium@452795      2588.6 +- 348.658      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/8986491514633029088

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


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

Looks like a flake and already recovered.