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

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


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

win-zenbook

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

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@405961  3.18397  0.0954127  5  good
chromium@405971  3.09477  0.0924557  5  good
chromium@405977  3.11692  0.0553899  5  good
chromium@405979  3.06477  0.110771   5  good
chromium@405980  3.0327   0.139762   5  good
chromium@405981  3.46191  0.0910174  5  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 629897

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2
Test Metric: v8-gc-scavenger_avg/v8-gc-scavenger_avg
Relative Change: 8.73%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/361
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005132180564084240


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

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

Ulan: the bisect failed to descend into the catapult roll, but it only had one CL: https://codereview.chromium.org/2138883002 "Fix computation of scroll amount in scroll actions." Is this expected?

Yes, that CL can affect benchmark workload.