Issue metadata
Sign in to add a comment
|
53.1% regression in battor.power_cases/after_load:power_avg on chromium-rel-mac-retina at 420360:420398 |
||||||||||||||||||||
Issue descriptionPerformance dashboard identified a 53.1% regression in battor.power_cases/after_load:power_avg on chromium-rel-mac-retina at revision range 420360:420398. Graph: https://chromeperf.appspot.com/report?masters=ChromiumPerf&bots=chromium-rel-mac-retina&tests=battor.power_cases%2Fafter_load%3Apower_avg&checked=after_load%3Apower_avg%2Cafter_load%3Apower_avg_ref%2Cref&rev=420398
,
Sep 26 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9000444294355511504
,
Sep 26 2016
=== Auto-CCing suspected CL author charliea@chromium.org === Hi charliea@chromium.org, the bisect results pointed to your CL below as possibly causing a regression. Please have a look at this info and see whether your CL be related. ===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : [telemetry] Disable the CPU tracing agent for BattOr benchmarks Author : charliea Commit description: It's causing indefinite hangs on https://goo.gl/EJZ4HY BUG= 647398 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq Review-Url: https://codereview.chromium.org/2344723003 Cr-Commit-Position: refs/heads/master@{#420360} Commit : 6c2fec5404e728502940032a8837a2bc7223d786 Date : Thu Sep 22 16:04:01 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@420359 5.89649 0.154864 5 good chromium@420360 9.18998 0.0411102 5 bad <-- chromium@420361 9.06377 0.131366 5 bad chromium@420362 9.00729 0.0885657 5 bad chromium@420364 9.0367 0.0741985 5 bad chromium@420369 9.06484 0.0953212 5 bad chromium@420379 8.99029 0.0627165 5 bad chromium@420398 9.02391 0.0887735 5 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 650279 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests battor.power_cases Test Metric: after_load:power_avg/after_load:power_avg Relative Change: 53.04% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1689 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000444294355511504 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5856660701052928 | 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
Marking as WontFix - this affected both the ref and non-ref builds, and has since improved again. Also, this is a change to the benchmark rather than to Chrome. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by rnep...@chromium.org
, Sep 26 2016