Issue metadata
Sign in to add a comment
|
1% regression in system_health.memory_mobile at 410299:410308 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 9 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9004795683734265904
,
Aug 9 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@410298 1936593 19334.9 8 good chromium@410308 1925052 0.0 8 bad Bisect job ran on: android_nexus7_perf_bisect Bug ID: 635929 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:v8:heap:effective_size_avg/load_games_lazors Relative Change: 0.71% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3174 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004795683734265904 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5810347634589696 | 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 10 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9004717079886089520
,
Aug 15 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9004240779786620208
,
Aug 16 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@410298 1940393 20220.4 8 good chromium@410322 1943157 5275.02 8 bad Bisect job ran on: android_nexus7_perf_bisect Bug ID: 635929 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:v8:effective_size_avg/load_games_lazors Relative Change: 0.02% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3208 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004240779786620208 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5900762316537856 | 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 17 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9004071890486222256
,
Aug 17 2016
,
Aug 18 2016
===== BISECT JOB RESULTS ===== Status: failed ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@410298 1927980 5421.6 8 good chromium@410321 1935568 6980.56 8 good chromium@410332 1936415 1.78885 5 good chromium@410332,v8@552601bb5f 1936415 1.78885 5 good chromium@410333 1945681 8829.79 5 bad chromium@410334 1972506 42139.6 5 bad chromium@410335 1941732 0.0 5 bad chromium@410338 1944972 0.0 5 bad chromium@410343 1948921 8829.79 5 bad Bisect job ran on: android_nexus7_perf_bisect Bug ID: 635929 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:v8:heap:effective_size_avg/load_games_lazors Relative Change: 0.99% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3215 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004071890486222256 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5840012956925952 | 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 18 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9003980162429391472
,
Aug 18 2016
===== BISECT JOB RESULTS ===== Status: failed ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@410298 1927980 5421.6 8 good chromium@410321 1935568 6980.56 8 good chromium@410332 1936415 1.78885 5 good chromium@410332,v8@552601bb5f 1936415 1.78885 5 good chromium@410333 1945681 8829.79 5 bad chromium@410334 1972506 42139.6 5 bad chromium@410335 1941732 0.0 5 bad chromium@410338 1944972 0.0 5 bad chromium@410343 1948921 8829.79 5 bad Bisect job ran on: android_nexus7_perf_bisect Bug ID: 635929 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:v8:heap:effective_size_avg/load_games_lazors Relative Change: 0.99% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3215 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004071890486222256 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5840012956925952 | 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 19 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9003887086128017936
,
Aug 19 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@410298 1932201 20220.6 8 good chromium@410308 1935129 19758.9 8 bad Bisect job ran on: android_nexus7_perf_bisect Bug ID: 635929 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:v8:heap:effective_size_avg/load_games_lazors Relative Change: 0.35% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3232 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004071890486222256 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5840012956925952 | 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 22 2016
This looks like noise, so I'm marking as WontFix.
,
Aug 30 2016
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by petrcermak@chromium.org
, Aug 9 2016