Issue metadata
Sign in to add a comment
|
13.7%-1086.3% regression in memory.top_10_mobile_stress at 421334:421420 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 28 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9000263101377753312
,
Sep 29 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@421377 207735 1983.06 18 good chromium@421387 208031 2247.21 18 bad Bisect job ran on: android_nexus5X_perf_bisect Bug ID: 651099 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --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/background/after_http_search_yahoo_com_search__ylt_p_google Relative Change: 1.19% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/703 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000263101377753312 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=4984869313052672 | 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!
,
Sep 30 2016
,
Dec 3 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8994342071909812400
,
Dec 3 2016
,
Dec 3 2016
=== PERF REGRESSION === === Auto-CCing suspected CL author dcheng@chromium.org === Hi dcheng@chromium.org, the bisect results pointed to your CL, please take a look at the results. ===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : Disallow redundant Bind calls. Author : dcheng Commit description: Make it a compile-time error base::Bind a base::Callback as the functor object with no additional args: in that case, just use the original callback! BUG=none R=danakj@chromium.org,tzik@chromium.org TBR=brettw@chromium.org Review-Url: https://codereview.chromium.org/2352853002 Cr-Commit-Position: refs/heads/master@{#420826} Commit : 172b6ad8f0213ba74d9447dbd08e32e1c7ce655a Date : Sat Sep 24 05:08:06 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@420591 66896696 711767 8 good chromium@420797 66919864 673488 8 good chromium@420823 67484984 1202068 8 good chromium@420825 67302328 678952 8 good chromium@420826 81861688 4309571 5 bad <-- chromium@420827 78413470 5056950 5 bad chromium@420830 79820856 6662142 5 bad chromium@420836 81121131 5949557 5 bad chromium@420849 80141982 5523830 5 bad chromium@420900 78632197 4746527 5 bad chromium@421002 81365458 5566647 5 bad chromium@421413 79876152 5494149 5 bad Bisect job ran on: android_nexus5_perf_bisect Bug ID: 651099 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=http.search.yahoo.com.search..ylt.p.google memory.top_10_mobile_stress Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google Relative Change: 19.40% Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4398 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994342071909812400 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=6348031539019776 | 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! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by rmcilroy@chromium.org
, Sep 28 2016