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

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


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

chromium-rel-mac11

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : tab_switching.typical_25
  Metric       : energy_consumption_mwh/energy_consumption_mwh
  Change       : 8.92% | 41.2599007937 -> 45.4142592593

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/949b36db0565e9a81fc50cbb1584d64d6090c147..babe852aafe34f62d5ac8fbfc252830b64eebeea


Revision             Result                  N
chromium@445283      41.2599 +- 5.46102      14       good
chromium@445284      ---                     ---      build failure
chromium@445285      42.0297 +- 7.55         13       bad
chromium@445287      45.4143 +- 4.10995      6        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 tab_switching.typical_25

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

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


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

looks a noise