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

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


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

chromium-rel-mac11-pro

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/load_social/load_social_twitter

Revision             Result                  N
chromium@463682      673.108 +- 386.286      21      good
chromium@463928      615.687 +- 348.032      21      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=load.social.twitter system_health.common_desktop

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

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


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

=== 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    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/load_social/load_social_twitter
  Change       : 10.10% | 680.724 -> 611.964952381

Revision             Result                  N
chromium@463682      680.724 +- 424.332      21      good
chromium@463805      661.284 +- 267.191      21      good
chromium@463836      658.142 +- 172.115      9       good
chromium@463844      676.676 +- 189.915      9       good
chromium@463845      584.109 +- 159.277      14      bad       <--
chromium@463846      596.783 +- 157.741      14      bad
chromium@463848      603.277 +- 141.422      14      bad
chromium@463852      585.207 +- 142.34       14      bad
chromium@463867      603.253 +- 115.405      14      bad
chromium@463928      611.965 +- 240.775      21      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=load.social.twitter system_health.common_desktop

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

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


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