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

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


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

android-webview-nexus5X

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: f1c1cd3f721af72be0aee8b5201000ffd6b522a2
  bad_revision : 1112a3a1a8ba9eedecf51ffeefb2990caad27070

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : blink_perf.layout
  Metric       : multicol_fixed-height-with-spanner-and-nested-tables/multicol_fixed-height-with-spanner-and-nested-tables
  Change       : 3.58% | 48.7177096636 -> 50.4601871729

Revision             Result                   N
chromium@518182      48.7177 +- 0.802788      6      good
chromium@518218      48.9911 +- 0.871339      6      good
chromium@518236      50.0187 +- 1.70603       9      bad
chromium@518253      50.4602 +- 0.788421      6      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

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 blink_perf.layout

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

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


For feedback, file a bug with component Speed>Bisection

This recovered.