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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgz4yZkAkM


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

android-nexus5X

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N    Good?
chromium@439093  20.3082  821.308  781  good
chromium@439116  19.5047  634.869  780  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 675673

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...cuteoverload.com smoothness.sync_scroll.key_mobile_sites_smooth
Test Metric: frame_times/http___cuteoverload.com
Relative Change: 3.96%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/1007
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8992821009749315024


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5311286043213824

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

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

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.