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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgkYisswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_sbD_AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_u_ysgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_sTC6AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvs3trQkM


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

chromium-rel-mac-hdd
chromium-rel-mac-retina
chromium-rel-mac10
chromium-rel-mac11

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/764
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Fix jank during mac resize
Author  : enne
Commit description:
  
Allow SetNeedsBeginFrames messages to be handled on Mac during resize.
If this message is not handled, then the renderer says that it needs
frames but the message is ignored because of the resize lock.  Then, the
browser never sends begin frame messages and the renderer then never is
able to produce a frame.  This means that it can't produce a frame of
the right size before the resize lock times out and there's jank on
screen.

R=ccameron@chromium.org,sievers@chromium.org
BUG= 632603 ,638561

Review-Url: https://codereview.chromium.org/2246613002
Cr-Commit-Position: refs/heads/master@{#413601}
Commit  : e5ce61d4966237e3572f3048a6ea39c7ba7d7c64
Date    : Tue Aug 23 00:27:11 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@413577  543.884  32.7537  5  good
chromium@413597  532.672  27.4089  5  good
chromium@413600  568.703  92.3188  5  good
chromium@413601  1075.98  196.663  5  bad    <--
chromium@413602  1159.02  68.0727  5  bad
chromium@413607  1134.81  43.8784  5  bad
chromium@413616  1138.51  102.773  5  bad
chromium@413655  1122.76  29.3999  5  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 643773

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.tough_layout_cases
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___mydiyclub.com
Relative Change: 106.43%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/832
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999798409997216592


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5839088748331008

| 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 Tests>AutoBisect.  Thank you!