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

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


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

android-webview-nexus5X

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

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

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

Revision             Result                  N
chromium@510972      866.022 +- 176.088      21      good
chromium@511161      884.304 +- 129.27       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=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/8964676707606850304


For feedback, file a bug with component Speed>Bisection

These timeseries have recovered and re-regressed several times since October.