Issue metadata
Sign in to add a comment
|
3.4%-93.9% regression in system_health.memory_mobile at 406421:406471 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 21 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006522748734942944
,
Jul 21 2016
===== 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@406420 1252459 190606 12 good chromium@406471 1303699 9945.91 8 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 630273 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_games-memory:chrome:all_processes:reported_by_chrome:sqlite:effective_size_avg/load_games_spychase Relative Change: 0.05% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1904 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006522748734942944 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5441162219880448 | 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!
,
Jul 25 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006155213106270176
,
Jul 25 2016
===== 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@406420 1142214 296390 12 good chromium@406471 1308767 8147.11 8 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 630273 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_games-memory:chrome:all_processes:reported_by_chrome:sqlite:effective_size_avg/load_games_spychase Relative Change: 0.16% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1911 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006155213106270176 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5254290575196160 | 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!
,
Aug 1 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005516093603593728
,
Aug 1 2016
Trying one last bisect. The regression has gone away so we might be able to close this if there's no definite finding.
,
Aug 2 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : [system-health] Run all SH stories in memory benchmarks Author : petrcermak Commit description: This patch modifies SH memory benchmarks (system_health.memory_desktop and system_health.memory_mobile) to run all SH stories: - load:* (already running) - browse:* (NEW) As a result, all SH stories will also run in the SH smoke test on the Chromium CQ (benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.*). *** NOTE TO SHERIFF *** This patch is very likely to cause failures in the System Health benchmarks (perf waterfall) and smoke tests (regular CQ). Please contact me before reverting. BUG=589726 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:mac_retina_perf_cq Review-Url: https://codereview.chromium.org/2159733002 Cr-Commit-Position: refs/heads/master@{#406309} Commit : 77952f99e4ae203b6b57005ce9e3476895426b96 Date : Tue Jul 19 18:03:07 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@406200 786566 17469.8 5 good chromium@406275 797698 3498.77 5 good chromium@406294 796475 3144.75 5 good chromium@406304 796622 2693.03 5 good chromium@406307 796622 3672.68 5 good chromium@406308 795376 2328.49 5 good chromium@406309 1427165 1352.37 5 bad <-- chromium@406313 1429955 3210.75 5 bad chromium@406350 1433491 3424.12 5 bad chromium@406500 1431024 4398.49 5 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 630273 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_tools-memory:chrome:all_processes:reported_by_chrome:sqlite:effective_size_avg/load_tools_stackoverflow Relative Change: 81.93% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1953 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005516093603593728 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5892328863039488 | 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!
,
Aug 30 2016
,
Aug 30 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by petrcermak@chromium.org
, Jul 21 2016