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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstContentfulPaint_avg/Regular-3G/YahooNews

Revision             Result                  N
chromium@515924      68065.7 +- 2464.77      21      good
chromium@516025      68014.9 +- 2953.7       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=YahooNews loading.mobile

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

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


For feedback, file a bug with component Speed>Bisection

Probably just noise.