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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6Oqn6woM


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

android-webview-nexus5X

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : thread_total_all_cpu_time_per_second/blank.html

Revision             Result                    N
chromium@449003      0.374274 +- 0.201197      21      good
chromium@449019      0.37668 +- 0.147738       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=blank.html thread_times.key_idle_power_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8988096635128193440

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5842614252732416


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Looks like this eventually progressed with point id: 460660. Closing.