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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgwtDZrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggo3pvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggu6D6QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgwrL74QoM


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

android-nexus5
android-webview-nexus6

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : smoothness.sync_scroll.key_mobile_sites_smooth
  Metric       : mean_input_event_latency/http___nytimes.com_
  Change       : 45.38% | 18.7412222222 -> 24.6183076923

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/d3920ccc81711676a41982bcae3a29b4142c6838..29e1187bcf8e4c2e9b322a0f7523fc627f5ef3b4


Revision             Result                  N
chromium@460357      18.7412 +- 13.2644      9        good
chromium@462313      20.6979 +- 15.7682      14       good
chromium@462558      21.3972 +- 13.6603      12       good
chromium@462619      21.3246 +- 12.6817      14       good
chromium@462635      21.2624 +- 14.1146      14       good
chromium@462643      18.0002 +- 16.5148      14       good
chromium@462644      20.216 +- 14.9318       8        good
chromium@462645      ---                     ---      build failure
chromium@462646      28.5689 +- 17.1713      8        bad
chromium@462647      23.1099 +- 26.4528      14       bad
chromium@462650      25.5879 +- 25.9334      20       bad
chromium@462681      27.5349 +- 15.7789      14       bad
chromium@462803      29.4914 +- 78.7443      21       bad
chromium@463291      24.8514 +- 25.2258      21       bad
chromium@464269      24.6183 +- 20.4293      13       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 --story-filter=http...nytimes.com. smoothness.sync_scroll.key_mobile_sites_smooth

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

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


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

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

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

Suspected Commit
  Author : chongz
  Commit : 232fbc4bc87a4c35ea8ab60e1f7ff8e4e8e14de5
  Date   : Fri Mar 31 20:14:35 2017
  Subject: Revert of Enable VsyncAlignedInput to Field Trial (patchset #1 id:40001 of https://codereview.chromium.org/2752363002/ )

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : smoothness.sync_scroll.key_mobile_sites_smooth
  Metric       : mean_input_event_latency/http___www.reddit.com_r_programming_comments_1g96ve
  Change       : 28.24% | 24.504 -> 31.4238333333

Revision             Result                  N
chromium@460340      24.504 +- 5.04416       6      good
chromium@460829      26.2233 +- 2.29874      6      good
chromium@461073      24.8227 +- 2.51451      6      good
chromium@461195      25.2503 +- 3.47742      6      good
chromium@461199      23.9858 +- 3.60247      6      good
chromium@461201      25.8444 +- 5.8127       9      good
chromium@461202      31.443 +- 3.40841       6      bad       <--
chromium@461203      30.255 +- 3.33712       6      bad
chromium@461211      32.614 +- 6.88049       6      bad
chromium@461226      32.9457 +- 4.52733      6      bad
chromium@461256      31.9478 +- 4.51447      6      bad
chromium@461317      32.579 +- 6.02893       6      bad
chromium@462293      33.2143 +- 4.68318      6      bad
chromium@464246      31.4238 +- 3.29233      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 --story-filter=http...www.reddit.com.r.programming.comments.1g96ve smoothness.sync_scroll.key_mobile_sites_smooth

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

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


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

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

Hi ccameron@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 : ccameron
  Commit : 29e1187bcf8e4c2e9b322a0f7523fc627f5ef3b4
  Date   : Thu Apr 06 22:17:52 2017
  Subject: Revert of cc: Always log shader compiler errors (patchset #2 id:20001 of https://codereview.chromium.org/2712033004/ )

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : smoothness.sync_scroll.key_mobile_sites_smooth
  Metric       : mean_input_event_latency/http___nytimes.com_
  Change       : 40.84% | 20.7235 -> 29.1873333333

Revision             Result                  N
chromium@460357      20.7235 +- 8.03059      6      good
chromium@462313      21.5775 +- 3.85935      6      good
chromium@462558      22.2752 +- 3.93225      6      good
chromium@462619      21.7192 +- 4.05501      6      good
chromium@462635      23.1958 +- 6.89842      9      good
chromium@462643      22.8729 +- 8.00792      9      good
chromium@462645      21.824 +- 2.59986       6      good
chromium@462646      27.6225 +- 6.37328      6      bad       <--
chromium@462647      27.3338 +- 4.63669      9      bad
chromium@462650      29.4658 +- 7.06021      6      bad
chromium@462680      27.0232 +- 4.95108      6      bad
chromium@462802      28.966 +- 4.25709       6      bad
chromium@463291      27.5048 +- 3.07688      6      bad
chromium@464269      29.1873 +- 4.57355      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 --story-filter=http...nytimes.com. smoothness.sync_scroll.key_mobile_sites_smooth

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

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


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