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

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


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

android-one

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

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

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


Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : smoothness.key_mobile_sites_smooth
  Metric       : input_event_latency_discrepancy/Pinterest


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=Pinterest smoothness.key_mobile_sites_smooth

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

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


For feedback, file a bug with component Speed>Bisection

This test was broken for months, bisect can't do this big a range, especially with failures.