Issue metadata
Sign in to add a comment
|
19.9%-253.8% regression in thread_times.tough_scrolling_cases at 405894:405918 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 28 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005886093256414288
,
Jul 28 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@405895 1.17899 0.0106299 12 good chromium@405910 1.17279 0.0135442 18 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 632342 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.tough_scrolling_cases Test Metric: thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame Relative Change: 0.66% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1457 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005886093256414288 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=4950968777572352 | 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 28 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005868289636689664
,
Jul 28 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005868284835232768
,
Jul 28 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@405895 13.5201 0.0865868 12 good chromium@405918 13.4681 0.110638 18 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 632342 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.tough_scrolling_cases Test Metric: thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame Relative Change: 0.85% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1458 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005868289636689664 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5777416341946368 | 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 28 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@405895 1.18505 0.0147788 12 good chromium@405918 1.18235 0.0135759 18 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 632342 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.tough_scrolling_cases Test Metric: thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame Relative Change: 0.96% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1459 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005868284835232768 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=6600629342961664 | 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 5 2016
+Annie, Roberto: I can't bisect.
,
Aug 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@405893 16.7372 0.0390534 18 good chromium@405910 16.7583 0.0294042 18 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 632342 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.tough_filters_cases Test Metric: frame_times/http___letmespellitoutforyou.com_samples_svg_filter_terrain.svg Relative Change: 0.04% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1552 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004853717944781936 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5891155296780288 | 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
,
Oct 6 2016
This is almost definitely 51630e3efbcde407cdc7c4e0f35cba88a2090601, but it's recovered regardless. +ericrk as FYI |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by rsch...@chromium.org
, Jul 28 2016