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

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


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

chromium-rel-mac11

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@433826  164.75   4.06202  24  good
chromium@433861  164.125  6.05186  24  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 669186

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests jetstream
Test Metric: Score/Score
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/1065
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994716153271460608


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

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

This is going to be difficult to impossible to bisect and it might be infrastructure. WontFix.

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