Issue metadata
Sign in to add a comment
|
4.6%-51.6% regression in smoothness.top_25_smooth at 407984:408405 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 29 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005812373607280848
,
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@408380 20.0518 0.581412 18 good chromium@408405 20.1039 0.36463 18 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 632655 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth Test Metric: mean_input_event_latency/http___sports.yahoo.com_ Relative Change: 1.12% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1463 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005812373607280848 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5781990347898880 | 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
The ref moves at the same time, I think we can close this.
,
Aug 2 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005435746909862176
,
Aug 2 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@408380 14.0116 0.545599 18 good chromium@408405 14.1152 0.397605 18 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 632655 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth Test Metric: mean_input_event_latency/Blogger Relative Change: 0.34% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1510 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005435746909862176 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5908416132808704 | 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 alexclarke@chromium.org
, Jul 29 2016