A typical error message:


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: e8e425a2fe4c4ee6ac307c9852b9fb5e93f18ab8
  bad_revision : 0b59d6f6f83e46081c827e216ab98e02b610413f

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/http_m_intl_taobao_com_group_purchase_html
  Change       : 2.50% | 23936524.0 -> 24535222.6667

Revision                       Result                   N
android-chrome@e8e425a2fe      23936524 +- 110483       6      good
android-chrome@0b59d6f6f8      24508940 +- 95014.3      6      bad
android-chrome@bd012d78b7      24535223 +- 212597       6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http.m.intl.taobao.com.group.purchase.html memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection