Issue metadata
Sign in to add a comment
|
1.1%-380% regression in system_health.memory_mobile at 406534:406601 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 21 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006532007814559696
,
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@406564 28672.0 7584.32 8 good chromium@406565 31278.5 4939.96 11 bad Bisect job ran on: android_nexus5X_perf_bisect Bug ID: 630202 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:v8:allocated_by_malloc:effective_size_avg/load_news_washingtonpost Relative Change: 0.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/351 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006532007814559696 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5080428185124864 | 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 21 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006500982818535520
,
Jul 21 2016
I'm convinced this was due to https://codereview.chromium.org/2162873002, but here's another bisect: https://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3854
,
Jul 22 2016
=== Auto-CCing suspected CL author ulan@chromium.org === Hi ulan@chromium.org, the bisect results pointed to your CL below as possibly causing a regression. Please have a look at this info and see whether your CL be related. ===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : [system health] Add flipboard to system health stories. Author : ulan Commit description: Flipboard on mobile exercises interesting workload, where news items are rendered using canvas. BUG=589726 Review-Url: https://codereview.chromium.org/2162873002 Cr-Commit-Position: refs/heads/master@{#406550} Commit : fd43bee2311ab250b3b6181ccd8be45092234eca Date : Wed Jul 20 14:30:46 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@406533 290380 0.0 5 good chromium@406549 290380 0.0 5 good chromium@406550 868054 0.0 5 bad <-- chromium@406551 868054 0.0 5 bad chromium@406553 868054 0.0 5 bad chromium@406557 868054 0.0 5 bad chromium@406565 868054 0.0 5 bad Bisect job ran on: android_nexus5_perf_bisect Bug ID: 630202 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_media-memory:chrome:all_processes:reported_by_chrome:web_cache:effective_size_avg/load_media_flickr Relative Change: 198.94% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3854 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006500982818535520 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5339183422373888 | 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 22 2016
This is not a real regression. It's due to a change in the SH story set.
,
Aug 30 2016
,
Aug 30 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by petrcermak@chromium.org
, Jul 21 2016