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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : cpu_utilization/garden2_10s.webm_browser

Revision             Result                  N
chromium@463205      5.15948 +- 1.27474      21      good
chromium@463267      4.9903 +- 1.60569       21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --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/8982387199203034880

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


| 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 Speed>Bisection.  Thank you!

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : cpu_utilization/garden2_10s.webm_browser

Revision             Result                  N
chromium@463205      5.15813 +- 2.7369       21      good
chromium@463267      5.07219 +- 1.75986      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --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/8982363846479161696

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


| 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 Speed>Bisection.  Thank you!

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : cpu_utilization/garden2_10s.webm_browser

Revision             Result                   N
chromium@463205      5.41652 +- 0.994863      14       good
chromium@463220      5.4399 +- 1.62444        21       good
chromium@463221      ---                      ---      build failure
chromium@463229      5.18381 +- 1.65491       21       unknown
chromium@463236      5.0746 +- 1.94455        21       bad
chromium@463267      4.93504 +- 1.29988       14       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --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/8982250599880799232

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


| 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 Speed>Bisection.  Thank you!

Looks like regression in cpu utilization is also present in ref build.