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

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


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

chromium-rel-mac-retina

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : cpu_utilization/video.html?src_crowd2160.webm

Revision             Result                   N
chromium@455646      6.88676 +- 0.419286      21      good
chromium@455719      6.91992 +- 0.373121      21      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 --story-filter=video.html.src.crowd2160.webm media.tough_video_cases

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

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


| 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/8982620010546037504

no bisect, closing as WontFix.