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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : smoothness.tough_scrolling_cases
  Metric       : mean_pixels_approximated/text_constant_full_page_raster_50000_pixels_per_second

Revision             Result                    N
chromium@511424      0.324476 +- 0.293883      21      good
chromium@511540      0.299524 +- 0.472186      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=text.constant.full.page.raster.50000.pixels.per.second smoothness.tough_scrolling_cases

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

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


For feedback, file a bug with component Speed>Bisection

Not sure why this wasn't reporting values before, but seems good that it is now.