Issue metadata
Sign in to add a comment
|
2.2%-3.2% regression in memory.top_10_mobile_stress at 424700:424722 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 13 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8998897600412660256
,
Oct 13 2016
===== BISECT JOB RESULTS ===== Status: completed === Bisection aborted === The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression. Please contact the the team (see below) if you believe this is in error. === Warnings === The following warnings were raised by the bisect job: * Bisect failed to reproduce the regression with enough confidence. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@424711 32411359 150422 18 good chromium@424716 32413692 210079 18 bad Bisect job ran on: android_nexus5_perf_bisect Bug ID: 655709 Test Command: 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_stress Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/http_www_baidu_com_s_word_google Relative Change: 0.34% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4243 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8998897600412660256 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5872216284069888 | 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!
,
Oct 14 2016
,
Dec 2 2016
Graphs look noisy; bisect failed to reproduce. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by lanwei@google.com
, Oct 13 2016