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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=0ac08523f40d0e545b5e0706fb459e649f0e9f6993f005ad979867d797e9ed6e


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

chromium-rel-mac11-pro

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

=== 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_pro_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : cpu_time_percentage_avg/video.html?src_tulip2.vp9.webm_background
  Change       : 0.59% | 0.223653756655 -> 0.224083208048

Suspected Commit Range
  17 commits in range
  https://chromium.googlesource.com/chromium/src/+log/2651d426c8c8fd0b85d9c7a8a85883b0579daf5d..9b20d8ef2273bd947156ccdf07af5aaa321be322


Revision             Result                      N
chromium@489885      0.223654 +- 0.00611946      14       good
chromium@489886      ---                         ---      build failure
---                  ---                         ---      too many build failures to list
chromium@489901      ---                         ---      build failure
chromium@489902      0.224228 +- 0.00575723      14       bad
chromium@489919      0.224083 +- 0.00207483      9        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.tulip2.vp9.webm.background media.tough_video_cases_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8972439769761421056


For feedback, file a bug with component Speed>Bisection