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

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


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

android-nexus5X

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

===== 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@435243  10963066  1870437  27  good
chromium@435263  10946861  2193693  27  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 670905

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=load.news.wikipedia system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_news/load_news_wikipedia
Relative Change: 0.15%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/949
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994341504471295232


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

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

 Issue 670904  has been merged into this issue.

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

Note: Most of these alerts don't appear to be a clear step pattern; test results appear to be bimodal.

===== 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@435243  58831758  20601710  27  good
chromium@435263  59718315  19544498  27  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 670905

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=load.social.facebook system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_social/load_social_facebook
Relative Change: 1.51%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/956
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994155548165787680


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

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

+sullivan

That pattern looks a lot like that dashboard problem, same issue?

What's the dashboard problem referred to here?

Note, there are several other groups of alerts that show a similar type of pattern, are these also all related?
 bug 670706 
 bug 670764 
bug 670765

The dashboard problem is https://github.com/catapult-project/catapult/issues/3050 -- looking at the alerts here, all but one are on Nexus 5X and the one that's on android-one is unclear and within the noise.

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_news/load_news_wikipedia

Revision             Result                   N
chromium@435243      11089338 +- 2101260      21      good
chromium@435263      11013624 +- 1933909      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=load.news.wikipedia system_health.memory_mobile

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

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


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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_baidu

Revision             Result                  N
chromium@435243      7904504 +- 90119.2      21      good
chromium@435263      7904296 +- 122173       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=load.search.baidu system_health.memory_mobile

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

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


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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/browse_news/browse_news_flipboard

Revision             Result                   N
chromium@435243      24033576 +- 1330455      21      good
chromium@435263      24031170 +- 1682089      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=browse.news.flipboard system_health.memory_mobile

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

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


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