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

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


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

chromium-rel-mac11

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

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

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : v8.google
  Metric       : v8_execution_cpu_total_avg/v8_execution_cpu_total_avg

Revision             Result                  N
chromium@448959      17.1071 +- 3.17457      21      good
chromium@449028      17.2164 +- 2.77004      21      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 v8.google

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

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


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