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

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


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

chromium-rel-mac-retina

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : performance_browser_tests
  Metric       : CastV2Performance_gpu_30fps_fast/send_to_renderer


To Run This Test
  ./src/out/Release/performance_browser_tests --test-launcher-print-test-stdio=always --enable-gpu

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

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


For feedback, file a bug with component Speed>Bisection

This regression hasn't recovered, but appears to be in the noise, so I don't expect bisect to reproduce.