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

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


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

chromium-rel-mac11

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

=== 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_crowd2160.webm

Revision             Result                     N
chromium@451237      408029571 +- 26115473      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.crowd2160.webm media.tough_video_cases

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

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


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

=== 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_crowd2160.webm
  Change       : 4.26% | 406670666.667 -> 423982666.667

Revision             Result                     N
chromium@451237      406670667 +- 11980434      6      good
chromium@451242      408319000 +- 8027391       6      good
chromium@451243      350000000 +- 0.0           5      good
chromium@451244      420294400 +- 7321381       5      bad       <--
chromium@451245      423897833 +- 14225758      6      bad
chromium@451247      422755167 +- 11790952      6      bad
chromium@451256      421119667 +- 19554341      6      bad
chromium@451275      418741833 +- 8823413       6      bad
chromium@451313      421597667 +- 13722149      6      bad
chromium@451389      423982667 +- 19785573      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.crowd2160.webm media.tough_video_cases

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

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


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