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

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


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

android-webview-nexus5X

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

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

Kicked new bisect.

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : blink_perf.layout
  Metric       : floats_100_100/floats_100_100

Revision             Result                  N
chromium@518182      561.604 +- 58.5182      21      good
chromium@518253      624.237 +- 781.302      21      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/8961047740790898608


For feedback, file a bug with component Speed>Bisection

These metrics just look bimodal.