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

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


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

chromium-rel-win10

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

===== 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@435374  195.483  193.935  27  good
chromium@435536  180.268  70.7565  27  bad

Bisect job ran on: winx64_10_perf_bisect
Bug ID: 671239

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.tough_energy_cases
Test Metric: energy_consumption_mwh/energy_consumption_mwh
Relative Change: 7.78%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/798
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994097139431869872


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

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

Ref build result moved at the same time.

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