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

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


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

android-nexus5

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

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

Suspected Commit
  Author : chongz
  Commit : 5a7f45dab8372cb7b80ee24dfb137a7ced2049ea
  Date   : Wed Mar 22 23:13:14 2017
  Subject: Enable VsyncAlignedInput to field trial

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : mean_main_thread_scroll_latency/mean_main_thread_scroll_latency
  Change       : 63.74% | 13.3616 -> 21.8785

Revision             Result                  N
chromium@458880      13.3616 +- 1.56099      5      good
chromium@458903      12.6417 +- 2.05271      6      good
chromium@458914      12.7943 +- 3.9651       6      good
chromium@458920      13.367 +- 1.07213       5      good
chromium@458921      21.9577 +- 1.32588      6      bad       <--
chromium@458922      22.128 +- 1.94552       6      bad
chromium@458923      21.7102 +- 2.30183      6      bad
chromium@458925      22.084 +- 1.8486        6      bad
chromium@458969      21.8785 +- 3.20096      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests scheduler.tough_scheduling_cases

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

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


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