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

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


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

android-nexus5
android-nexus5X
android-one
android-webview-nexus5X

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : frame_times/Docs  (1 open document tab)

Revision             Result                   N
chromium@499269      17.6355 +- 0.208985      14      good
chromium@502500      45.9503 +- 15.8883       14      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=Docs...1.open.document.tab. smoothness.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/8968031402996758720


For feedback, file a bug with component Speed>Bisection

This is successfully running the 2 reference values, and then failing to find a midpoint that works, eventually hitting the 24 hour limit.

Every run fails out with errors. From https://chromium-review.googlesource.com/c/chromium/src/+/669743 it sounds as if smoothness as broken for a while.

Bisect unable to find culprit, this regression exists in stable. Ignoring.