Bug for testing bisect configs |
||
Issue descriptionNot a real bug, just testing bisect configs.
,
Oct 7 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999465472623125040
,
Oct 7 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999465377004610768
,
Oct 7 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999465350362261152
,
Oct 8 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@421161 4346224 10103.4 17 good chromium@421186 4347174 8803.07 17 bad Bisect job ran on: android_nexus6_perf_bisect Bug ID: 653838 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.top_10_mobile Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:heap:effective_size_avg/memory:chrome:all_processes:reported_by_chrome:v8:heap:effective_size_avg Relative Change: 0.32% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2624 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999465350362261152 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5852003782098944 | 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 8 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@421840 1984704 0.0 18 good chromium@421900 1984704 0.0 18 bad Bisect job ran on: android_nexus5_perf_bisect Bug ID: 653838 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.top_10_mobile Test Metric: memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/background/after_http_en_m_wikipedia_org_wiki_Science Relative Change: 0.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4201 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999465511779052112 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=6408062728929280 | 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 8 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@415945 1984704 0.0 18 good chromium@415986 1984704 0.0 18 bad Bisect job ran on: android_nexus5_perf_bisect Bug ID: 653838 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.top_10_mobile Test Metric: memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/background/after_https_m_facebook_com_rihanna Relative Change: 0.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4202 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999465472623125040 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5223426728394752 | 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 8 2016
===== BISECT JOB RESULTS ===== Status: failed ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@421829 7831485 99137.2 8 good chromium@421854 7946907 169756 8 good chromium@421856 7843318 180686 5 good chromium@421858 8266292 137589 8 bad chromium@421861 8375382 176693 8 bad chromium@421867 8294599 19833.0 5 bad chromium@421879 8378046 244683 8 bad Bisect job ran on: android_nexus6_perf_bisect Bug ID: 653838 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.top_10_mobile Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:heap:effective_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus Relative Change: 7.36% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2623 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999465377004610768 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5854888121073664 | 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!
,
Nov 25 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 7 2016