Issue metadata
Sign in to add a comment
|
3.7%-5.4% regression in page_cycler.intl_hi_ru at 408133:408179 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 29 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005812347376997104
,
Jul 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@408132 1679.0 15.8476 8 good chromium@408179 1686.49 7.23873 8 bad Bisect job ran on: android_nexus5X_perf_bisect Bug ID: 632658 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.intl_hi_ru Test Metric: warm_times/page_load_time Relative Change: 0.31% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/387 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005812347376997104 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5287567939862528 | 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!
,
Jul 29 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005791003812266464
,
Jul 29 2016
Trying again.
,
Jul 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@408000 1674.53 24.7662 12 good chromium@408200 1688.88 17.4983 8 bad Bisect job ran on: android_nexus5X_perf_bisect Bug ID: 632658 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.intl_hi_ru Test Metric: warm_times/page_load_time Relative Change: 1.14% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/390 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005791003812266464 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5810354311921664 | 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!
,
Aug 1 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005541259345841776
,
Aug 1 2016
Trying with more iterations.
,
Aug 1 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005541212180260192
,
Aug 1 2016
Trying with more iterations.
,
Aug 1 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@408000 1672.88 21.6208 8 good chromium@408200 1681.96 12.8875 8 bad Bisect job ran on: android_nexus5X_perf_bisect Bug ID: 632658 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.intl_hi_ru Test Metric: warm_times/page_load_time Relative Change: 1.20% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/406 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005541259345841776 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5890732678709248 | 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!
,
Aug 18 2016
Perf sheriff ping: reminder to follow up on possible performance issues
,
Sep 23 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9000698638823752416
,
Sep 23 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/693 Failure reason: the build has failed. Additional errors: Either of the initial "good" or "bad" revisions failed to be tested or built.
,
Oct 6 2016
Perf sheriff fixit: unsetting owners where reporter==owner, to clarify the current member of the rotation is responsible for triage.
,
Oct 6 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999521838438406128
,
Oct 6 2016
re-kicking a bisect. If this fails, I'll CC the test owners for recommended next steps.
,
Oct 6 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/736 Failure reason: the build has failed. Additional errors: Either of the initial "good" or "bad" revisions failed to be tested or built.
,
Nov 22 2016
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982620337027924240
,
Jul 27 2017
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by alexclarke@chromium.org
, Jul 29 2016