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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgg8CF7wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_fXwvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgg5iU-QgM


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

win-zenbook

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N   Good?
chromium@427414  12.1626  0.232409  18  good
chromium@427456  12.2691  0.330403  18  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 660545

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests tab_switching.five_blank_pages
Test Metric: energy_consumption_mwh/energy_consumption_mwh
Relative Change: 0.77%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/572
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997521734440854640


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

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

Reference bot also regressed. This is a test environment/HW issue.