Issue metadata
Sign in to add a comment
|
5.1%-9.8% regression in memory.top_10_mobile_stress at 451274:451359 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8987029506036997824
,
Feb 22 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_yandex_ru_touchsearch_text_science Revision Result N chromium@451273 4346924 +- 21536.3 6 good chromium@451334 4864941 +- 21746.0 6 bad Please refer to the following doc on diagnosing memory regressions: https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8987029506036997824 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5879799500767232 | 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 Speed>Bisection. Thank you!
,
Feb 27 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8986483906654961248
,
Feb 27 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8986483903235828416
,
Mar 11 2017
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982636259133548320
,
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 rsch...@chromium.org
, Feb 21 2017