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

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


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

chromium-rel-mac11-pro

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

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

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

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


Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : startup.warm.blank_page
  Metric       : first_main_frame_load_time/first_main_frame_load_time


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=2 --also-run-disabled-tests startup.warm.blank_page

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

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


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

=== Auto-CCing suspected CL author samans@chromium.org ===

Hi samans@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : samans
  Commit : 2040988b1345e6ce738bd03ab7ccd5f4b73a956b
  Date   : Tue Apr 11 23:58:35 2017
  Subject: Use MojoCompositorFrameSink in RendererCompositorFrameSink

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : startup.warm.blank_page
  Metric       : first_main_frame_load_time/first_main_frame_load_time
  Change       : 23.79% | 863.833333333 -> 666.666666667

Revision             Result                  N
chromium@463682      863.833 +- 58.6245      6       good
chromium@463805      858.556 +- 177.308      9       good
chromium@463836      854.0 +- 75.3923        6       good
chromium@463844      857.0 +- 63.6239        6       good
chromium@463845      660.0 +- 103.363        6       bad       <--
chromium@463846      642.667 +- 89.6065      6       bad
chromium@463848      665.833 +- 122.429      6       bad
chromium@463852      661.0 +- 91.214         6       bad
chromium@463867      704.429 +- 363.326      14      bad
chromium@463928      666.667 +- 140.178      9       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=2 --also-run-disabled-tests startup.warm.blank_page

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

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


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