Issue metadata
Sign in to add a comment
|
1%-11.3% regression in system_health.memory_mobile at 406557:406625 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 25 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006152375440085264
,
Jul 26 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@406569 855888 0.0 8 good chromium@406589 855888 0.0 8 bad Bisect job ran on: android_nexus5_perf_bisect Bug ID: 631060 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:sqlite:effective_size_avg/load_search_yandex Relative Change: 0.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3867 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006152375440085264 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5759727695298560 | 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/9005155769358414368
,
Aug 15 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9004245436474143472
,
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@406565 111317576 1314558 8 good chromium@406625 112484040 841191 8 bad Bisect job ran on: android_nexus5_perf_bisect Bug ID: 631060 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_stackoverflow Relative Change: 1.03% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3995 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004245436474143472 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5809356285673472 | 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/9003879288034535744
,
Aug 30 2016
,
Aug 30 2016
,
Oct 3 2016
,
Nov 18 2016
,
May 1 2017
This has been accounted for on a macro scale and could be closed as wontfix.
,
May 1 2017
This has been accounted for on a macro scale and could be closed as wontfix.
,
May 2 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 3 2018
Obsolete perf regression alert with more than one year of inactivity. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by petrcermak@chromium.org
, Jul 25 2016