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

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


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

android-webview-nexus5X

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstMeaningfulPaint_avg/Regular-3G/https___m.facebook.com_?soft_messages

Revision             Result                  N
chromium@456171      8556.23 +- 4420.67      21      good
chromium@456232      8325.04 +- 2740.17      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=https...m.facebook.com..soft.messages loading.mobile

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

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


| 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!

This recovered.