Issue metadata
Sign in to add a comment
|
8.5%-31.9% regression in thread_times.key_idle_power_cases at 416627:416682 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 9 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9002017702008309680
,
Sep 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@416627 0.40667 0.0675328 18 good chromium@416661 0.440377 0.0710945 18 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 645374 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.key_idle_power_cases Test Metric: thread_total_all_cpu_time_per_second/request-animation-frame.html Relative Change: 7.93% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2101 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002017702008309680 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5855403089330176 | 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 6 2016
Perf fixit: removing perf sheriff as owner of bugs to clarify that the rotation is responsible for triage.
,
Nov 17 2016
This really is not a thing. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by briander...@chromium.org
, Sep 9 2016