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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=0b100d82bd5a152b4cac01da03683d1a1bf889d4947200c6cbbb777303d4bebb


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

android-nexus5X
android-webview-nexus5X
android-webview-nexus6

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : smoothness.simple_mobile_sites
  Metric       : mean_input_event_latency/http___m.nytimes.com_

Revision             Result                   N
chromium@498628      14.5637 +- 0.799266      14      good
chromium@498936      15.9104 +- 0.853911      14      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...m.nytimes.com. smoothness.simple_mobile_sites

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8969256964037229120


For feedback, file a bug with component Speed>Bisection

This came back down.