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

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


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

android-webview-nexus5X

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

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

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

Revision             Result                  N
chromium@514571      604.695 +- 66.8814      21      good
chromium@514641      692.36 +- 815.715       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/8963323370738271472


For feedback, file a bug with component Speed>Bisection

Looks like we reverted to the previous average.