Issue metadata
Sign in to add a comment
|
3.2%-135.9% regression in system_health.memory_mobile (jig-jag increase pattern) at 435104:435108 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 2 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8994372063884685392
,
Dec 2 2016
===== BISECT JOB RESULTS ===== Status: failed === Bisection aborted === The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence. Please contact the the team (see below) if you believe this is in error. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@435103 3994583 3635.73 27 good chromium@435108 3994390 3295.66 27 bad Bisect job ran on: android_nexus5X_perf_bisect Bug ID: 670706 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.hackernews system_health.memory_mobile Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_news/load_news_hackernews Relative Change: None Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/937 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994372063884685392 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=6738395412299776 | 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!
,
Dec 6 2016
Note: These alerts show the same pattern as in several other recent bugs filed for system_health.memory_mobile; this should probably be combined with several other bugs.
,
Dec 6 2016
,
Dec 6 2016
Likely related: bug 670764 bug 670765 bug 670905
,
Dec 7 2016
Non-Nexus 5X alerts split off into bug 671851 . The jig-jag shape in the remaining graphs can be explained by https://github.com/catapult-project/catapult/issues/3050. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by qyears...@chromium.org
, Dec 2 2016