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

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


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

android-nexus5

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

=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Step('Check bisect finished on revision chromium@511397.fetch file c3be6ac562e5c1a8815d505969b7d8077836d90c:DEPS') failed with return_code 1


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : smoothness.sync_scroll.key_mobile_sites_smooth
  Metric       : frame_times/http___worldjournal.com_

Revision             Result                  N
chromium@511393      21.949 +- 3.41029       6      good
chromium@511396      22.6825 +- 1.98378      6      good
chromium@511397      22.3505 +- 2.40888      6      good
chromium@511398      26.2954 +- 2.17314      6      bad
chromium@511402      26.7179 +- 2.14166      6      bad
chromium@511410      26.381 +- 1.46327       6      bad
chromium@511426      26.8507 +- 2.47566      6      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...worldjournal.com. smoothness.sync_scroll.key_mobile_sites_smooth

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8964185857741798576


For feedback, file a bug with component Speed>Bisection

Bisect got to a catapult roll, looks like this is a metrics change.