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

=== 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: 3aeae9f58d9507abd2ecef33041fc2685eb79613
  bad_revision : 3091104c4600073df5584780a4a0798205b26d69

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


Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_www_amazon_com_gp_aw_s_k_nexus

Revision             Result                 N
chromium@482283      2971794 +- 133542      14       good
chromium@482319      2978457 +- 165281      14       good
chromium@482337      2966739 +- 279817      14       good
chromium@482346      2977234 +- 104321      14       good
chromium@482349      ---                    ---      build failure
chromium@482350      ---                    ---      build failure
chromium@482351      ---                    ---      build failure
chromium@482352      ---                    ---      build failure
chromium@482354      3008592 +- 122391      14       bad
chromium@482424      3023119 +- 115698      14       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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile

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

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


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

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

Alerts for this bug:
https://chromeperf.appspot.com/group_report?bug_id=737525

All small (< 50KiB) regressions, appear to be a pair of a land/revert pattern, and the build was broken while the regression got introduced.

So, not worth to investigate further.

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_www_amazon_com_gp_aw_s_k_nexus

Revision             Result                 N
chromium@482283      2983146 +- 173122      21      good
chromium@482424      3002546 +- 104544      21      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests 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/8975452682064615344


For feedback, file a bug with component Speed>Bisection