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

Since I can't look at the stdout of the run I can't really give this any deeper look, but given that the tests haven't changed in while, wouldn't be more likely indicate an issue elsewhere (whether in infrastructure or code; the bisect ought to help indicate the latter.)

=== BISECT JOB RESULTS ===
NO Test failure found

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : blink_perf.svg
  Metric       : AzLizardBenjiPark/AzLizardBenjiPark

Revision             Exit Code      N
chromium@462559      0 +- N/A       20      good
chromium@462588      0 +- N/A       20      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 blink_perf.svg

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

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


| 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!

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.