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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguryXtAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2tae6AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2v_3qgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgupjnvgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmpuRlAgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2tKD-gkM


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

android-nexus5X
android-webview-nexus5X
android-webview-nexus6
chromium-rel-mac11-pro

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : Optimize:duration_avg/browse_news/browse_news_washingtonpost
  Change       : 275.47% | 2.30504761905 -> 8.65485714286

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/ad403f1b07abd269492fbe074e04963ec69edd1c..c39c757894f7a9a68a4ed4bf9942f94eece2b6a0


Revision             Result                   N
chromium@473238      2.30505 +- 3.05775       21       good
chromium@473252      2.49767 +- 0.77764       9        good
chromium@473256      2.76329 +- 2.26152       14       good
chromium@473257      2.45617 +- 0.572439      6        good
chromium@473258      ---                      ---      build failure
chromium@473259      9.89257 +- 10.4355       14       bad
chromium@473266      8.65486 +- 18.8658       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=browse.news.washingtonpost v8.runtimestats.browsing_mobile

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

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


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