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

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


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

chromium-rel-mac11-air

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

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

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : tab_switching.tough_energy_cases
  Metric       : energy_consumption_mwh/energy_consumption_mwh

Revision             Result                  N
chromium@455494      35.5021 +- 47.1203      21      good
chromium@455712      32.252 +- 2.11251       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 tab_switching.tough_energy_cases

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

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


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

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.