Issue metadata
Sign in to add a comment
|
27.8% regression in blink_perf.canvas at 423567:423661 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 10 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999170520804637488
,
Oct 10 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@423566 297.214 21.4865 18 good chromium@423661 284.468 22.009 18 bad Bisect job ran on: winx64nvidia_perf_bisect Bug ID: 654469 Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.canvas Test Metric: upload-video-to-sub-texture/upload-video-to-sub-texture Relative Change: 7.30% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1905 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999170520804637488 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5275265960247296 | 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
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999076537805866544
,
Oct 11 2016
Probably noise, should be closed if bisect doesn't find anything the second time.
,
Oct 11 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@423566 299.394 28.1111 18 good chromium@423661 290.885 30.3318 18 bad Bisect job ran on: winx64nvidia_perf_bisect Bug ID: 654469 Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.canvas Test Metric: upload-video-to-sub-texture/upload-video-to-sub-texture Relative Change: 6.69% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1909 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999076537805866544 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5776425829793792 | 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 17 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by qyears...@chromium.org
, Oct 10 2016