Issue metadata
Sign in to add a comment
|
6.7% regression in memory.top_10_mobile at 424402:424417 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 13 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8998897402194435024
,
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@424401 25080372 556326 18 good chromium@424417 25171167 424486 18 bad Bisect job ran on: android_nexus7_perf_bisect Bug ID: 655711 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 Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background/after_https_m_facebook_com_rihanna Relative Change: 0.52% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3394 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8998897402194435024 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5804725503524864 | 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
,
Oct 18 2016
The range makes me suspect this could be the same as issue 655134.
,
Oct 18 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8998465828899933328
,
Oct 18 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4250 Failure reason: the build has failed due to infrastructure failure.
,
Oct 18 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8998456086443930192
,
Oct 31 2016
Annie, Dave, the bisect job in #8 appears to have completed, but results weren't posted. Any ideas? Will also retry.
,
Oct 31 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8997280156020358032
,
Oct 31 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@424401 24273005 405174 18 good chromium@424417 24123046 300520 18 bad Bisect job ran on: android_nexus7_perf_bisect Bug ID: 655711 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=https.m.facebook.com.rihanna memory.top_10_mobile Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background/after_https_m_facebook_com_rihanna Relative Change: 1.81% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3438 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997280156020358032 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5775198521917440 | 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 31 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8997272957467361232
,
Oct 31 2016
Re: #9: sometimes there is a delay, looks like it did complete though.
,
Oct 31 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@424401 25217076 632803 18 good chromium@424417 24908624 850459 18 bad Bisect job ran on: android_nexus7_perf_bisect Bug ID: 655711 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 Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background/after_https_m_facebook_com_rihanna Relative Change: 0.23% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3439 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997272957467361232 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5220229288820736 | 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!
,
Dec 19 2016
Regression won't reproduce. And it's old enough that we don't have logs any more.
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982596490747413360 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by lanwei@google.com
, Oct 13 2016