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

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


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

android-nexus6

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

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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : smoothness.sync_scroll.key_mobile_sites_smooth
  Metric       : first_gesture_scroll_update_latency/Pinterest

Revision             Result                  N
chromium@496588      82.3709 +- 119.671      21      good
chromium@496661      78.4502 +- 141.977      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=Pinterest smoothness.sync_scroll.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/8970294976167947520


For feedback, file a bug with component Speed>Bisection

The "regression" is the test coming back online after months, too big a range to bisect.