Issue metadata
Sign in to add a comment
|
A zero-to-nonzero regression in system_health.memory_mobile at 436397:436483 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 7 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8993924383214242192
,
Dec 7 2016
===== BISECT JOB RESULTS ===== Status: failed === Bisection aborted === The bisect was aborted because root Please contact the the team (see below) if you believe this is in error. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@436396 N/A N/A 0 good chromium@436483 1258291 2297315 5 bad Bisect job ran on: android_one_perf_bisect Bug ID: 672073 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=background.news.nytimes system_health.memory_mobile Test Metric: memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/background_news/background_news_nytimes Relative Change: None Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1855 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993924383214242192 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5814363296890880 | 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 12 2016
,
Dec 12 2016
Error message isn't helpful but looks like bot_update failed during re-testing the reference values, logged crbug.com/673432 on that.
,
Jul 27 2017
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by tdres...@chromium.org
, Dec 7 2016