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

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


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

android-one

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.top_25_smooth
  Metric       : mean_input_event_latency/Blogger

Revision             Result                 N
chromium@526714      22.1287 +- 3.9141      21      good
chromium@526855      21.724 +- 3.51877      21      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=Blogger smoothness.gpu_rasterization.top_25_smooth

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

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


For feedback, file a bug with component Speed>Bisection

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14e02122840000

Kicked off another bisect with wider range.

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14e02122840000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14976b2d840000

Trying again with a wider range.

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14976b2d840000

Checked the values on the bisect, it's definitely producing data and not repro-ing. sadrul, any ideas what to do?

Looks like https://chromium-review.googlesource.com/c/849313/ landed in the regression change, and the smoothness tests do generate scroll events. So this looks related.

sahel@: Mind taking a look? It doesn't look like this caused an outright regression, but it definitely made the data quite noisy.

The regression is on android and https://chromium-review.googlesource.com/c/849313/ is only for GSUs with wheel event source, I don't think it can be the cause of this regression.

please feel free to assign it back to me if you still think https://chromium-review.googlesource.com/c/849313/ might be the cause of regression.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/168b75fb440000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/168b75fb440000

I an unable to look at data from 2018 at all right now. The latest I see is from July 2017 [1]. Very weird; I do remember seeing the regression in the link in comment #1 ... but not anymore. I will check back again later.

[1] https://chromeperf.appspot.com/report?sid=d2f4139dea9d307d305494f37400883f75e436bd04b7a5734518b4b8572568d4

Re #17: the pages in this pageset have been renamed, here are the correct charts: https://chromeperf.appspot.com/report?sid=94bc9596cefcbfb53bc5de5048e1598f518300ebb14122e52a0354282013dcce

sadrul: any idea what the next action on this bug should be?

I don't see any related regression on other sites, or other somewhat related metrics (e.g. main_thread_scroll_latency, first_gesture_scroll_update_latency etc.).

I am going to start a yet another pin-point (if nothing else to stress test the bots), and probably close as WontFix.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16bfd8c8240000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/16bfd8c8240000

All of the attempts failed. See the individual attempts for details on each error.