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

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


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

chromium-rel-mac-hdd

===== 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 Value  Std. Dev.   Num Values  Good?
chromium@386810         956.416667  19.218638   12          good
chromium@386879         965.25      49.488094   8           bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 604010

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests power.top_25
Test Metric: idle_wakeups_total/idle_wakeups_total
Relative Change: 1.67%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/484
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9015284031158234288


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

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

re-kicked bisect with modified range.

===== 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 Value  Std. Dev.   Num Values  Good?
chromium@386805         957.416667  45.653753   12          good
chromium@386869         946.0       42.311768   8           bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 604010

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests power.top_25
Test Metric: idle_wakeups_total/idle_wakeups_total
Relative Change: 1.14%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/489
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9014712094407233536


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

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

re-kicked bisect with modified range.

===== 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@386800  980.667  37.7094  9  good
chromium@386865  962.125  30.4792  8  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 604010

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests power.top_25
Test Metric: idle_wakeups_total/idle_wakeups_total
Relative Change: 3.03%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/509
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013794480577724736


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

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

I wonder if this is real?  I note the ref jumped and there seemed to be a data stoppage in the non-ref graph.

I kicked off another wide bisect, if that fails to find a regression I suggest closing this.

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


===== SUSPECTED CL(s) =====
Subject : Blacklist CALayer overlays on 10.10
Author  : ccameron
Commit description:
  
This is causing hangs on 10.10. Forcing fallback to the GL renderer
makes the issue go away according to people who have seen the
issue.

So far all reports of this issue are on the following dual-GPU
combination:
  iGPU: 0x8086, 0x0166
  dGPU: 0x10de, 0x0fd5
If this improves histograms, we will try to limit the scope of
the blacklist to just this combination.

BUG= 580616 

Review URL: https://codereview.chromium.org/1873283002

Cr-Commit-Position: refs/heads/master@{#386783}
Commit  : d5c58b5bfba2721be8681f67e784279e2030c423
Date    : Tue Apr 12 19:55:31 2016


===== TESTED REVISIONS =====
Revision         Mean   Std Dev  N  Good?
chromium@385253  685.6  9.31665  5  good
chromium@386068  677.8  18.8997  5  good
chromium@386470  666.4  15.6461  5  good
chromium@386672  675.2  18.5391  5  good
chromium@386775  675.6  26.5763  5  good
chromium@386779  673.8  25.3318  5  good
chromium@386781  683.2  20.5353  5  good
chromium@386782  682.6  5.50454  5  good
chromium@386783  956.8  35.6959  5  bad    <--
chromium@386790  955.6  7.73305  5  bad
chromium@386805  966.2  30.8334  5  bad
chromium@386834  966.8  11.6919  5  bad
chromium@386879  957.4  23.9958  5  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 604010

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests power.top_25
Test Metric: idle_wakeups_total/idle_wakeups_total
Relative Change: 39.64%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/541
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013147227183772496


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

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