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 17 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 4982.78 626.198 9 good chromium@400042 5111.75 713.124 12 bad Bisect job ran on: mac_hdd_perf_bisect Bug ID: 620841 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: 8.47% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/584 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009668517774818944 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5819478277881856 | 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
No alerts. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by benjhayden@chromium.org
, Jun 16 2016