regression in system_health.memory_desktop at 407939:407983 |
|||
Issue description
,
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@407938 676992 0.0 12 good chromium@407983 676992 0.0 8 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 637852 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop Test Metric: browse_news-memory:chrome:all_processes:reported_by_chrome:sqlite:effective_size_avg/browse_news_reddit Relative Change: 0.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1569 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004248510375224832 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5882883575644160 | 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/9003879034471713376
,
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@407783 676992 0.0 12 good chromium@407983 676992 0.0 8 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 637852 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop Test Metric: browse_news-memory:chrome:all_processes:reported_by_chrome:sqlite:effective_size_avg/browse_news_reddit Relative Change: 0.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1591 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003879034471713376 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5303976946302976 | 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
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9003619634594941632
,
Aug 22 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@407415 676992 0.0 12 good chromium@407983 676992 0.0 8 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 637852 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop Test Metric: browse_news-memory:chrome:all_processes:reported_by_chrome:sqlite:effective_size_avg/browse_news_reddit Relative Change: 0.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1600 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003619634594941632 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5775051475910656 | 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 23 2016
Similarly to issue 633223 , the bisect can't reproduce the regression, so I'm going to assume it was due to an infrastructure change.
,
Aug 30 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 15 2016