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

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


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

android-nexus5

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

=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Infra Failure: Step('Re-testing reference range.Retesting BAD revision.gsutil download_build_product (2)') returned 1


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : mean_input_event_latency/mean_input_event_latency

Revision             Result                  N
chromium@450938      13.2669 +- 3.94345      14      good
chromium@451005      13.3985 +- 1.80321      9       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/8986733343626176720

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


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

The graphs seem to indicate a "trend" of regressing, but it could also be considered "in the noise." Bisects aren't working, so I can't isolate the exact change.

skyostil/brianderson: As owners, I'll leave it up to you how to proceed here.

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

Let's see if the bisect comes back this time. Didn't spot anything in the changelog.

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : mean_input_event_latency/mean_input_event_latency


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

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


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

Looks like there was definitely something here -- it's especially apparent with the blank page with a touch handler. It seems to have recovered now but I didn't spot any clear culprit from the log -- maybe this revert related to rAF aligned input?

https://chromium.googlesource.com/chromium/src/+/550f89fa439bba1a6aad2d2e343259bca9d0e731

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

=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Infra Failure: Step('Re-testing reference range.Retesting BAD revision.gsutil download_build_product (2)') returned 1


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : mean_input_event_latency/mean_input_event_latency

Revision             Result                  N
chromium@450938      13.2669 +- 3.94345      14      good
chromium@451005      13.3985 +- 1.80321      9       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/8982596473206605680

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


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