Issue metadata
Sign in to add a comment
|
85.4% regression in performance_browser_tests at 474185:474272 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 30 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978177366484701392
,
May 30 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: winx64nvidia_perf_bisect Benchmark : performance_browser_tests Metric : CastV2Performance_gpu_60fps/capture_duration Change : 35.76% | 11.6151781429 -> 15.9618517143 Suspected Commit Range 17 commits in range https://chromium.googlesource.com/chromium/src/+log/d10a8c41ef88566b25aff3f763ac7ec605bac4ea..94274172ed5f2f5f5b2ead35f07e5e011a73e3b4 Revision Result N chromium@474184 11.6152 +- 2.4638 14 good chromium@474185 11.1803 +- 1.04187 9 good chromium@474186 --- --- build failure --- --- --- too many build failures to list chromium@474201 --- --- build failure chromium@474202 16.4421 +- 6.65577 9 bad chromium@474206 16.1448 +- 8.11649 9 bad chromium@474228 15.3865 +- 13.5754 21 bad chromium@474272 15.9619 +- 7.78603 14 bad To Run This Test .\src\out\Release_x64\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978177366484701392 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4503835059421184 | 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!
,
May 31 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by toyoshim@chromium.org
, May 30 2017