Issue metadata
Sign in to add a comment
|
3.6%-204.9% regression in memory.top_10_mobile_stress at 422374:424542 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 12 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999004404215277280
,
Oct 12 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@424458 3803705 1863551 18 good chromium@424460 4529038 1643951 18 bad Bisect job ran on: android_one_perf_bisect Bug ID: 655131 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:ashmem:proportional_resident_size_avg/foreground/https_www_google_co_uk_hl_en_q_science Relative Change: 41.42% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1712 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999004404215277280 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5309544765325312 | 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 26 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8997728045172506400
,
Oct 26 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@424000 4885504 1216992 18 good chromium@424486 5204764 147535 18 bad Bisect job ran on: android_one_perf_bisect Bug ID: 655131 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.www.google.co.uk.hl.en.q.science memory.top_10_mobile_stress Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:ashmem:proportional_resident_size_avg/foreground/https_www_google_co_uk_hl_en_q_science Relative Change: 3.07% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1763 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997728045172506400 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5790549930409984 | 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 6 2017
Archiving as bisection is difficult and there's been no movement. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by tdres...@chromium.org
, Oct 12 2016