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

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


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

android-one

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

=== 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.simple_mobile_sites
  Metric       : input_event_latency_discrepancy/http___www.ebay.co.uk_


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.ebay.co.uk. 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/8964185888531619856


For feedback, file a bug with component Speed>Bisection

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

This timeseries does not appear to have recovered, so I broadened the revision range. It's very noisy, so if bisect still fails, then let's Archive and move on.

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

Hi bokan@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 : David Bokan
  Commit : dbab215523c8d77a7b54fcf3776357b079c36899
  Date   : Tue Oct 24 14:24:10 2017
  Subject: Fix telemetry gesture speeds

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : smoothness.simple_mobile_sites
  Metric       : input_event_latency_discrepancy/http___www.ebay.co.uk_

Revision                                 Result                  N
chromium@510804                          246.727 +- 135.76       6      good
chromium@511104                          288.366 +- 162.272      6      good
chromium@511254                          242.058 +- 93.4637      6      good
chromium@511329                          217.39 +- 100.019       6      good
chromium@511366                          220.01 +- 181.782       6      good
chromium@511385                          284.441 +- 96.1427      6      good
chromium@511394                          241.33 +- 66.0516       6      good
chromium@511397                          229.472 +- 119.383      6      good
chromium@511397,catapult@f9691b256a      245.384 +- 145.157      6      good
chromium@511397,catapult@dbab215523      621.167 +- 428.936      6      bad       <--
chromium@511397,catapult@2f4cf37a9f      741.676 +- 300.812      6      bad
chromium@511398                          743.405 +- 595.569      6      bad
chromium@511399                          561.992 +- 361.73       6      bad
chromium@511403                          494.144 +- 217.535      6      bad
chromium@512002                          587.41 +- 85.0188       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.ebay.co.uk. 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/8957922650702333136


For feedback, file a bug with component Speed>Bisection

The CL fixed how gestures are dispatched in telemetry so a change in metrics is to be expected but doesn't represent a user-facing regression.