Issue metadata
Sign in to add a comment
|
11.1%-91.6% regression in startup.warm.blank_page at 421375:421447 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 3 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999819240714177232
,
Oct 3 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@421386 2.95371 0.723651 18 good chromium@421420 2.88211 0.824083 18 bad Bisect job ran on: android_nexus6_perf_bisect Bug ID: 652246 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2 Test Metric: v8-gc-incremental-step_max/v8-gc-incremental-step_max Relative Change: 11.29% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2595 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999819240714177232 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5325932095602688 | 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 4 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999731012929182016
,
Oct 4 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@421374 3.47639 3.28679 18 good chromium@421420 3.62639 3.19548 18 bad Bisect job ran on: android_nexus6_perf_bisect Bug ID: 652246 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2 Test Metric: v8-gc-incremental-step_max/facebook Relative Change: 8.31% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2600 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999731012929182016 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5833887542935552 | 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 5 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999635918350807920
,
Oct 6 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@421374 3.77244 2.94405 18 good chromium@421420 4.16989 2.9449 18 bad Bisect job ran on: android_nexus6_perf_bisect Bug ID: 652246 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2 Test Metric: v8-gc-incremental-step_max/facebook Relative Change: 36.34% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2612 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999635918350807920 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=6079516185722880 | 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 11 2016
Issue 652245 has been merged into this issue.
,
Oct 11 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999065682393504176
,
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@421374 2.27737 0.423665 18 good chromium@421420 2.48117 0.709249 18 bad Bisect job ran on: android_nexus6_perf_bisect Bug ID: 652246 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2 Test Metric: v8-gc-incremental-step_max/v8-gc-incremental-step_max Relative Change: 4.39% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2640 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999065682393504176 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5778137240043520 | 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 13 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8998905048170944320
,
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@421374 2.29249 0.519446 18 good chromium@421420 2.39286 0.594984 18 bad Bisect job ran on: android_nexus6_perf_bisect Bug ID: 652246 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2 Test Metric: v8-gc-incremental-step_max/v8-gc-incremental-step_max Relative Change: 6.23% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2643 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8998905048170944320 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5876829414490112 | 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 2 2016
No ref build; graphs are somewhat noisy; bisect failed to reproduce many times. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by tdres...@chromium.org
, Oct 3 2016