Issue metadata
Sign in to add a comment
|
444.1% regression in smoothness.top_25_smooth at 392209:392232 |
||||||||||||||||||
Issue descriptionNot sure if this regression is actually real or not. I'll see what the bots find if anything and double check with a trace.
,
May 9 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@392208 3.25 0.917409 12 good chromium@392232 3.65983 1.58313 18 bad Bisect job ran on: win_8_perf_bisect Bug ID: 610239 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: first_gesture_scroll_update_latency/https___www.google.com__hl_en_q_barack+obama Relative Change: 31.11% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/1936 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013151744038482512 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5868561818451968 | 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!
,
May 9 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@392200 1.55806 0.994097 18 good chromium@392250 3.63761 5.52996 18 bad Bisect job ran on: winx64intel_perf_bisect Bug ID: 610239 Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth Test Metric: first_gesture_scroll_update_latency/https___www.google.com__hl_en_q_barack+obama Relative Change: 126.80% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/916 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013151591655420272 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5830606655586304 | 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!
,
May 9 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@392150 6.45606 5.48906 18 good chromium@392250 5.03242 2.31618 12 bad Bisect job ran on: win_8_perf_bisect Bug ID: 610239 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: first_gesture_scroll_update_latency/https___www.google.com__hl_en_q_barack+obama Relative Change: 0.99% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/1937 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013151720696838144 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5776464968941568 | 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!
,
May 9 2016
Trying a std dev bisect.
,
May 26 2016
This seems to have recovered, closing. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by alexclarke@chromium.org
, May 9 2016