Issue metadata
Sign in to add a comment
|
A zero-to-nonzero to 1.1% regression in system_health.memory_mobile at 406091:406420 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 25 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006152040216970368
,
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@406392 36864.0 0.0 8 good chromium@406403 36864.0 0.0 8 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 631064 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:discardable:effective_size_avg/load_tools_drive Relative Change: 0.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1913 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006152040216970368 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5854532454580224 | 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 5 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005152691531559408
,
Aug 5 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1984 Failure reason: the build has failed.
,
Aug 5 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005124822991468736
,
Aug 6 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1984 Failure reason: the build has failed.
,
Aug 7 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005032776177414528
,
Aug 7 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@406392 2802693 393453 12 good chromium@406403 2911437 307577 8 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 631064 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_news-memory:chrome:all_processes:reported_by_chrome:dom_storage:effective_size_avg/load_news_wikipedia Relative Change: 6.51% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1991 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005124822991468736 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5772682516234240 | 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 8 2016
This is almost definitely r406372, but it's quite a big regression on some values (tens of MiBs), so I'm going to run another bisect just to make sure.
,
Aug 8 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9004902646155994720
,
Aug 9 2016
===== BISECT JOB RESULTS ===== Status: failed ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@406090 206351427 2139853 5 good chromium@406255 205670877 3788359 5 good chromium@406338 204421597 4280670 5 good chromium@406359 203186243 1897262 5 good chromium@406369 202867574 1635260 5 good chromium@406371 203629430 1217085 5 good chromium@406372 257606526 13870787 5 bad chromium@406374 263253355 874161 5 bad chromium@406379 258359779 14848588 5 bad chromium@406420 266454174 2267427 5 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 631064 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_os:system_memory:proportional_resident_size_avg/load_tools_weather Relative Change: 29.13% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1995 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004902646155994720 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5873561231687680 | 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 9 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9004837842795241248
,
Aug 9 2016
===== BISECT JOB RESULTS ===== Status: failed ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@406090 206351427 2139853 5 good chromium@406255 205670877 3788359 5 good chromium@406338 204421597 4280670 5 good chromium@406359 203186243 1897262 5 good chromium@406369 202867574 1635260 5 good chromium@406371 203629430 1217085 5 good chromium@406372 257606526 13870787 5 bad chromium@406374 263253355 874161 5 bad chromium@406379 258359779 14848588 5 bad chromium@406420 266454174 2267427 5 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 631064 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_os:system_memory:proportional_resident_size_avg/load_tools_weather Relative Change: 29.13% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1995 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004902646155994720 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5873561231687680 | 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/9004745738073943920
,
Aug 10 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : [system health] Fix load:news:washingtonpost and browse:news:washingtonpost on Nexus9. Author : ulan Commit description: Washingtonpost popup window on Nexus9 does not have "Close" button. This patch checks for the presence of the button before clicking it. BUG= 629163 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq Review-Url: https://codereview.chromium.org/2159253002 Cr-Commit-Position: refs/heads/master@{#406372} Commit : 50adac87a62954be18180cbf74590a54a9d70dd4 Date : Tue Jul 19 20:37:53 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@406090 204879939 2846527 5 good chromium@406255 203911440 2788379 5 good chromium@406338 205015926 3025263 5 good chromium@406359 203169245 4291662 5 good chromium@406369 203708688 4176863 5 good chromium@406371 201146435 1845752 5 good chromium@406372 264092421 3032210 5 bad <-- chromium@406374 262896798 1269396 5 bad chromium@406379 265230494 3674551 5 bad chromium@406420 267183878 5139846 5 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 631064 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_os:system_memory:proportional_resident_size_avg/load_tools_weather Relative Change: 30.41% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2000 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004902646155994720 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5873561231687680 | 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 25 2016