Issue metadata
Sign in to add a comment
|
69.2% regression in power.trivial_scroll at 400009:400042 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 16 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@400008 3921.83 248.92 18 good chromium@400042 3971.06 284.369 18 bad Bisect job ran on: mac_hdd_perf_bisect Bug ID: 620842 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests power.trivial_scroll Test Metric: idle_wakeups_total/idle_wakeups_total Relative Change: 0.03% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/586 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009668502548392992 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5774391065968640 | 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!
,
Jun 16 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@400008 4266.67 322.689 18 good chromium@400042 4321.06 414.804 18 bad Bisect job ran on: mac_hdd_perf_bisect Bug ID: 620842 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests power.trivial_scroll Test Metric: idle_wakeups_total/idle_wakeups_total Relative Change: 2.12% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/585 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009668515606523200 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5781714253643776 | 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!
,
Jun 24 2016
Kicked off a bisect in https://chromeperf.appspot.com/buildbucket_job_status/9008940361096303440
,
Jun 24 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@400008 3737.61 737.873 18 good chromium@400042 3920.0 465.679 18 bad Bisect job ran on: mac_hdd_perf_bisect Bug ID: 620842 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests power.trivial_scroll Test Metric: idle_wakeups_total/TrivialScrollingPageSharedPageState Relative Change: 1.97% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/601 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9008940361096303440 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5327354897891328 | 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 1 2016
This metric recovered, before being made worse again. Also these are clear non-regressions when bisected, this suggests something changed in the bots. Close this maybe?
,
Jul 4 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 11 2016
This has recovered. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by benjhayden@chromium.org
, Jun 16 2016