Issue metadata
Sign in to add a comment
|
2.7%-7.4% regression in memory.top_10_mobile at 435969:436054 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 5 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8994093167822731296
,
Dec 5 2016
===== BISECT JOB RESULTS ===== Status: failed === Bisection aborted === The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence. Please contact the the team (see below) if you believe this is in error. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@435998 3233460 446329 27 good chromium@436006 3226922 507510 27 bad Bisect job ran on: android_nexus6_perf_bisect Bug ID: 671257 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 Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_https_www_google_co_uk_hl_en_q_science Relative Change: 0.20% Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2803 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994093167822731296 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5310684160589824 | 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 6 2016
Recovered.
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982620254184706304 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by qyears...@chromium.org
, Dec 5 2016