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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxIzq-QoM


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstContentfulPaint_avg/Regular-3G/https___www.google.co.id__q_pengiriman+bunga

Revision             Result                  N
chromium@451843      10307.7 +- 15993.5      21      good
chromium@453053      11285.0 +- 16556.5      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=https...www.google.co.id..q.pengiriman.bunga loading.mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8985784809036966928

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5889993773416448


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!