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

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


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

chromium-rel-mac-retina

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : power.top_10
  Metric       : idle_wakeups_total/idle_wakeups_total

Revision             Result                  N
chromium@441656      254.729 +- 946.635      48      good
chromium@441771      254.333 +- 932.435      48      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 power.top_10

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

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


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

This could've been nothing.