Issue metadata
Sign in to add a comment
|
74.1% regression in webrtc.stress at 430639:430660 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982428550518652944
,
Apr 13 2017
=== Auto-CCing suspected CL author ehmaldonado@chromium.org === Hi ehmaldonado@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : ehmaldonado Commit : 967024f84d0fc6ada6db5bace52e7b6ca027669b Date : Tue Nov 08 17:28:45 2016 Subject: Update telemetry benchmark to stress-test WebRTC. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : webrtc.stress Metric : cpu_utilization/cpu_utilization_gpu Change : 57.46% | 4.40688295198 -> 6.93917208568 Revision Result N chromium@430638 4.40688 +- 1.39078 6 good chromium@430641 4.37562 +- 0.779748 6 good chromium@430642 4.41942 +- 0.328305 6 good chromium@430643 7.19893 +- 0.97062 6 bad <-- chromium@430644 7.52043 +- 1.72153 6 bad chromium@430649 7.45647 +- 2.26241 6 bad chromium@430660 6.93917 +- 0.514539 6 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests webrtc.stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982428550518652944 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6411625164177408 | 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 Speed>Bisection. Thank you!
,
Apr 18 2017
This was intended. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by guidou@chromium.org
, Apr 13 2017