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

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


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

android-nexus5

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@424532  88161788  3235218  18  good
chromium@424578  88254118  3227869  18  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 655264

Test Command: 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_stress
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google
Relative Change: 0.52%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4236
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8998978850296392384


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5830848299925504

| 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 Tests>AutoBisect.  Thank you!

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@424400  80536564  977174   93  good
chromium@424432  80450047  849149   62  good
chromium@424448  80601120  1089581  62  good
chromium@424456  80367049  1013649  41  good
chromium@424460  80332058  1192898  41  good
chromium@424462  80627369  1122766  41  good
chromium@424463  82874200  2860255  41  bad
chromium@424525  82713126  3252045  93  bad
chromium@424650  82755781  3185664  93  bad
chromium@424900  83061118  3178609  41  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 655264

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http.search.yahoo.com.search..ylt.p.google memory.top_10_mobile_stress
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google
Relative Change: 4.71%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4294
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997726153254371664


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5345002102718464

| 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 Tests>AutoBisect.  Thank you!

These regressions happened before M56 branch. M56 is now in stable. These regressions made it to the stable channel. Marking wontfix.

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

=== 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_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google

Suspected Commit Range
  1 commits in range
  https://chromium.googlesource.com/chromium/src/+log/5b99bb23039bb2457a509282f8fc9b839072ca8a..eb735dcc1ff10e3c333345bd0902c1baed793543


Revision             Result                   N
chromium@424400      80536564 +- 977174       93      good
chromium@424432      80450047 +- 849149       62      good
chromium@424448      80601120 +- 1089581      62      good
chromium@424456      80367049 +- 1013649      41      good
chromium@424460      80332058 +- 1192898      41      good
chromium@424462      80627369 +- 1122766      41      good
chromium@424463      82874200 +- 2860255      41      bad
chromium@424525      82713126 +- 3252045      93      bad
chromium@424650      82755781 +- 3185664      93      bad
chromium@424900      83061118 +- 3178609      41      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 --story-filter=http.search.yahoo.com.search..ylt.p.google memory.top_10_mobile_stress

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

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


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