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

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


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

android-nexus5X

Bisect re-kicked with wider revision range.

Details on the below link:
========================
https://chromeperf.appspot.com/group_report?bug_id=602328

Thank you!

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@385910         55.777104   6.850745    18          good
chromium@386040         99.743424   51.296966   18          bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 602328

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.fling.simple_mobile_sites
Test Metric: input_event_latency_discrepancy/input_event_latency_discrepancy
Relative Change: 117.81%
Score: 0

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


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

| 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 re-kicked with wider revision range as the previous one failed.

Details on the below link:
-------------------------
https://chromeperf.appspot.com/group_report?bug_id=602328

Thank you!

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@385910  55.9404  6.15101  18  good
chromium@386030  104.183  50.2523  18  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 602328

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.fling.simple_mobile_sites
Test Metric: input_event_latency_discrepancy/input_event_latency_discrepancy
Relative Change: 100.61%
Score: 0

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


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

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

Two of the regressions seem to hba gone back to normal. Kicked off one on the webview chart that is still regressed: https://chromeperf.appspot.com/buildbucket_job_status/9013131504634204992

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N   Good?
chromium@384356  16.9638  0.158202  18  good
chromium@387000  17.2306  0.328622  18  bad

Bisect job ran on: android_webview_aosp_perf_bisect
Bug ID: 602328

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.fling.simple_mobile_sites
Test Metric: frame_times/http___m.nytimes.com_
Relative Change: 0.30%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_webview_aosp_perf_bisect/builds/135
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013131504634204992


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

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

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The alerts for this bug include two that have no ref build results (could be noise) and one that looks recovered; no clear evidence of a real regression. Bisect also failed to reproduce a regression.