Issue metadata
Sign in to add a comment
|
3.8% regression in memory.top_10_mobile_stress at 443465:443513 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8990282605525358560
,
Jan 16 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_m_intl_taobao_com_group_purchase_html Revision Result N chromium@443464 6495453 +- 95688.7 21 good chromium@443513 6504080 +- 98912.2 21 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 --story-filter=http.m.intl.taobao.com.group.purchase.html memory.top_10_mobile_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8990282605525358560 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5883700195098624 | 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 20 2017
,
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 nzolghadr@chromium.org
, Jan 16 2017