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

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


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

android-one

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

===== 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@432185  18.149   100.939  1345  good
chromium@432200  18.1359  102.57   1344  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 667902

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...news.yahoo.com smoothness.sync_scroll.key_mobile_sites_smooth
Test Metric: frame_times/http___news.yahoo.com
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1823
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995256953262173280


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

| 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/8995084314948296752

===== 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@432130  18.0827  89.1024  1349  good
chromium@432210  18.0154  80.023   1351  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 667902

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...news.yahoo.com smoothness.sync_scroll.key_mobile_sites_smooth
Test Metric: frame_times/http___news.yahoo.com
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1829
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995084314948296752


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

| 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/8995082291684664160

===== 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@432085  18.0686  79.871   1350  good
chromium@432290  18.0421  83.9189  1350  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 667902

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...news.yahoo.com smoothness.sync_scroll.key_mobile_sites_smooth
Test Metric: frame_times/http___news.yahoo.com
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1830
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995082291684664160


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

| 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!

Bisect couldn't reproduce; no ref build results.

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

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : smoothness.sync_scroll.key_mobile_sites_smooth
  Metric       : frame_times/http___news.yahoo.com

Revision             Result                   N
chromium@432185      18.0293 +- 0.454661      21      good
chromium@432200      17.9886 +- 0.120918      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=http...news.yahoo.com smoothness.sync_scroll.key_mobile_sites_smooth

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982651646337946448

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5226808021090304


| 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 Speed>Bisection.  Thank you!

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