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

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


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

android-nexus5

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : frame_times/http___www.ebay.com

Revision             Result                  N
chromium@511426      17.4483 +- 1.45896      21      good
chromium@511521      17.6896 +- 2.26928      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...www.ebay.com 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/8964184795853076144


For feedback, file a bug with component Speed>Bisection

Bisect can't repro, and seems to be a return to previous levels.