Issue metadata
Sign in to add a comment
|
A zero-to-nonzero to 1.2% regression in memory.top_10_mobile at 446361:448563 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 8 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988257919254661088
,
Feb 8 2017
=== BISECT JOB RESULTS === NO Perf regression found, tests failed to produce values Bisect Details Configuration: android_one_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/background/after_https_mobile_twitter_com_justinbieber_skip_interstitial_true Revision Result N chromium@448563 5771264 +- 0.0 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=https.mobile.twitter.com.justinbieber.skip.interstitial.true memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8988257919254661088 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5574319356248064 | 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!
,
Mar 11 2017
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982611904178576240
,
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 lanwei@chromium.org
, Feb 8 2017