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

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


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

android-one

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@410003  92822.4  6239.52  5  good
chromium@410027  94487.2  7266.08  5  good
chromium@410033  89902.4  289.794  5  good
chromium@410035  89902.4  289.794  5  good
chromium@410036  220148   0.0      5  bad
chromium@410038  220148   0.0      5  bad
chromium@410049  220148   0.0      5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 635492

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_search-memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/load_search_google
Relative Change: 137.17%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1501
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004896375966387520


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

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

Story set change (r410036).

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@410003  92822.4  6239.52  5  good
chromium@410027  94487.2  7266.08  5  good
chromium@410033  89902.4  289.794  5  good
chromium@410035  89902.4  289.794  5  good
chromium@410036  220148   0.0      5  bad
chromium@410038  220148   0.0      5  bad
chromium@410049  220148   0.0      5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 635492

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_search-memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/load_search_google
Relative Change: 137.17%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1501
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004896375966387520


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

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

=== Auto-CCing suspected CL author petrcermak@chromium.org ===

Hi petrcermak@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : [system-health] Re-enable full Google Search story on mobile
Author  : petrcermak
Commit description:
  
The original patch adding the story
(https://codereview.chromium.org/2173943003/) was reverted
(https://codereview.chromium.org/2173943003/) due to failures on
Windows. While the problem hasn't been fixed yet
(http://crbug.com/634343), this patch re-enables the story on mobile.

*** NOTE TO SHERIFFS ***
REGULAR CQ:
If this patch causes failures in telemetry_perf_tests, please add the
test name
(benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.system_health.memory_mobile.search:portal:google)
to _DISABLED_TESTS in tools/perf/benchmarks/system_health_smoke_test.py
instead of reverting.
PERF CQ:
If this patch causes failures in
system_health.memory_mobile[.reference], please change
SUPPORTED_PLATFORMS in
tools/perf/page_sets/system_health/searching_stories.py to
platforms.NO_PLATFORMS instead of reverting or disabling the benchmark.

BUG=589726,634343

Review-Url: https://codereview.chromium.org/2217113002
Cr-Commit-Position: refs/heads/master@{#410036}
Commit  : 7632abc40c4d27ef688f5a6ced98b2a56e51187e
Date    : Fri Aug 05 12:11:40 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@410003  89772.8  354.924  5  good
chromium@410027  90032.0  0.0      5  good
chromium@410033  90032.0  0.0      5  good
chromium@410035  90356.8  726.275  5  good
chromium@410036  220148   0.0      4  bad    <--
chromium@410038  220148   0.0      5  bad
chromium@410049  220148   0.0      5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 635492

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_search-memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/load_search_google
Relative Change: 145.23%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1505
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004896375966387520


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

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