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

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


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

android-webview-nexus5X

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstPaint_avg/long_running_tools/long_running_tools_gmail-foreground


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=long.running.tools.gmail.foreground system_health.common_mobile

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

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


For feedback, file a bug with component Speed>Bisection

+tdresser: more up-and-down first paint metrics. In this case, we don't have bisect results because the tests didn't output values, but everything went back down so I'm WontFix-ing. But the browse_tools_maps chart is pretty noisy.

Thanks.

Actually WontFix-ing per #4