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

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


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

android-webview-nexus5X

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : loading.mobile
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/warm/FlipKart


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=FlipKart loading.mobile

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

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


For feedback, file a bug with component Speed>Bisection

This recovered; looks bimodal.