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

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


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

chromium-rel-mac11

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N    Good?
chromium@437362  517.865  4534.69  156  good
chromium@437379  509.397  4309.6   156  good
chromium@437380  528.083  4810.35  156  good
chromium@437395  648.596  5161.19  156  bad
chromium@437418  647.327  5302.15  156  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 673403

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests media.tough_video_cases
Test Metric: idle_wakeups_browser/idle_wakeups_browser
Relative Change: 25.00%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/1117
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993457895347666032


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

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

Not sure why the bisect job stopped at a range of 15 CLs.
Here is the list:
http://test-results.appspot.com/revision_range?start=437380&end=437395

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/1123
Failure reason: the build has failed due to infrastructure failure.

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

Started bisect: https://chromeperf.appspot.com/buildbucket_job_status/8990561510760414384

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : idle_wakeups_browser/idle_wakeups_browser
  Change       : 23.44% | 524.724358974 -> 647.711538462

Suspected Commit Range
  15 commits in range
  https://chromium.googlesource.com/chromium/src/+log/f32ade75b611e31c6f43914a93c3f7067bcc8cce..5c49d183f4713e682965e831387a1f4bdac32034


Revision             Result                  N
chromium@437362      524.724 +- 52.2829      6        good
chromium@437379      527.872 +- 38.6313      6        good
chromium@437380      536.423 +- 19.4254      6        good
chromium@437381      ---                     ---      build failure
---                  ---                     ---      too many build failures to list
chromium@437394      ---                     ---      build failure
chromium@437395      635.564 +- 47.0586      6        bad
chromium@437418      647.712 +- 21.6521      6        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 media.tough_video_cases

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

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


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

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