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

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


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

chromium-rel-mac11

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : gpu_average_frequency_hz/video.html?src_smpte_3840x2160_60fps_vp9.webm

Revision             Result                N
chromium@451237      350000000 +- 0.0      21      good

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.smpte.3840x2160.60fps.vp9.webm media.tough_video_cases

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

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


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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : ccameron
  Commit : 3b6fe6da979b8d9e084160ce6d8b7bd83f3aa878
  Date   : Fri Feb 17 06:21:58 2017
  Subject: color: Don't use QCMS for transforms unless necessary

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : gpu_average_frequency_hz/video.html?src_smpte_3840x2160_60fps_vp9.webm
  Change       : 3.38% | 467146000.0 -> 482933666.667

Revision             Result                     N
chromium@451237      467146000 +- 15699322      6      good
chromium@451243      474262500 +- 9955185       6      good
chromium@451244      493821667 +- 14442609      6      bad       <--
chromium@451245      494978500 +- 17984271      6      bad
chromium@451246      486659500 +- 6555568       6      bad
chromium@451248      487142333 +- 8681779       6      bad
chromium@451259      490827833 +- 21831050      6      bad
chromium@451280      482933667 +- 24884001      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 --story-filter=video.html.src.smpte.3840x2160.60fps.vp9.webm media.tough_video_cases

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

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


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