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

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


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

android-nexus7v2
chromium-rel-mac11-air

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

=== Auto-CCing suspected CL author chrome-release-bot@chromium.org ===

Hi chrome-release-bot@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : chrome-release-bot
  Commit : b528d28ed46e08084f9b1a6a0e81fad09419176d
  Date   : Sun May 07 03:03:32 2017
  Subject: Updating trunk VERSION from 3092.0 to 3093.0

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : speedometer
  Metric       : BackboneJS-TodoMVC/BackboneJS-TodoMVC
  Change       : 3.31% | 349.130642857 -> 352.083964286

Revision             Result                  N
chromium@469893      349.131 +- 28.6358      14      good
chromium@469894      356.37 +- 22.0659       14      bad       <--
chromium@469897      356.968 +- 24.7962      14      bad
chromium@469898      352.084 +- 18.973       14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer

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

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


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

seems to be a flake