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

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@431022  15392199  2254189  21  good
chromium@431075  15463098  2146920  21  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 674876

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.en.m.wikipedia.org.wiki.Science memory.top_10_mobile
Test Metric: memory:chrome:renderer_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background/after_http_en_m_wikipedia_org_wiki_Science
Relative Change: 0.46%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3559
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993118851907345088


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

| 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/8993110188010527472

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@431022  15352896  5303584  21  good
chromium@431075  15402682  6178457  21  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 674876

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
Test Metric: memory:chrome:renderer_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background/after_http_en_m_wikipedia_org_wiki_Science
Relative Change: 0.32%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3561
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993110188010527472


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

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

Failing to reproduce a clear regression, both with and without the story-filter.

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

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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background/after_http_en_m_wikipedia_org_wiki_Science

Revision             Result                   N
chromium@431022      15392199 +- 2254189      21      good
chromium@431075      15463098 +- 2146920      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 --story-filter=http.en.m.wikipedia.org.wiki.Science memory.top_10_mobile

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

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


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