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

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


===== SUSPECTED CL(s) =====
Subject : Updating trunk VERSION from 2809.0 to 2810.0
Author  : chrome-cron
Commit description:
  
Cr-Commit-Position: refs/heads/master@{#408031}
Commit  : 056ef60b443abd3f43c78074f120196b25f30dca
Date    : Wed Jul 27 03:15:10 2016


===== TESTED REVISIONS =====
Revision         Exit Code  Std Dev  N  Good?
chromium@407984  0          N/A      1  good
chromium@408014  0          N/A      1  good
chromium@408029  0          N/A      1  good
chromium@408030  0          N/A      1  good
chromium@408031  1          N/A      1  bad    <--
chromium@408033  1          N/A      1  bad
chromium@408036  1          N/A      1  bad
chromium@408043  1          N/A      1  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 632039

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests power.top_25
Test Metric: energy_consumption_mwh/energy_consumption_mwh
Relative Change: Zero to non-zero
Score: 0.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1454
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005965954156707888


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

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

Blocking issue 632392 is marked as fixed and also not seeing this failure anymore on Mac perf bots.
Fadi@ Should this be marked as fixed?

Friendly sheriff ping; should this be closed?

(According to the Perf Bot Sheriffing guide, Pri-1 build bot bugs should be pinged daily. Please close the issue if it's already been fixed.)