Issue metadata
Sign in to add a comment
|
8.1% regression in system_health.memory_mobile at 439382:439397 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 29 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8991948545368172432
,
Dec 29 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@439381 13108474 2000927 21 good chromium@439397 13215611 1873726 21 bad Bisect job ran on: android_nexus5_perf_bisect Bug ID: 677430 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.reddit system_health.memory_mobile Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_news/load_news_reddit Relative Change: 0.82% Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4488 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8991948545368172432 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5856375140253696 | 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!
,
Jan 2 2017
Blocking on crbug.com/671156 for no-repro on system_health.memory_mobile. Using --story-filter affects reproducibility on this benchmark, try running without it.
,
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 alexclarke@chromium.org
, Dec 29 2016