Issue metadata
Sign in to add a comment
|
dEQP-VK.api.smoke failing on R58 branch for SKL-Y and APL |
||||||||||||||||||||||
Issue descriptionWe seem to be failing some dEQP-VK tests on the R58 branch, for example https://uberchromeos-server38.corp.google.com/new_tko/#tab_id=test_detail_view&object_id=445132888 ... 03/07 08:36:31.428 INFO | graphics_dEQP:0566| Test results: 03/07 08:36:31.428 INFO | graphics_dEQP:0567| {'ResourceError': 2, 'Pass': 4} 03/07 08:36:31.430 INFO | graphics_dEQP:0589| Completed all tests. Saw 6 tests, 4 passes and 2 failures. 03/07 08:36:31.431 DEBUG| test:0389| Test failed due to Failed: on skylake 2/6 tests failed.. Exception log follows the after_iteration_hooks. 03/07 08:36:31.432 DEBUG| test:0392| starting after_iteration_hooks 03/07 08:36:31.436 DEBUG| base_utils:0185| Running 'logger "autotest finished iteration /usr/local/autotest/results/default/graphics_dEQP/sysinfo/iteration.1"' 03/07 08:36:31.447 DEBUG| test:0395| after_iteration_hooks completed 03/07 08:36:31.449 WARNI| test:0615| The test failed with the following exception Traceback (most recent call last): File "/usr/local/autotest/common_lib/test.py", line 609, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/usr/local/autotest/common_lib/test.py", line 817, in _call_test_function return func(*args, **dargs) File "/usr/local/autotest/common_lib/test.py", line 470, in execute dargs) File "/usr/local/autotest/common_lib/test.py", line 347, in _call_run_once_with_retry postprocess_profiled_run, args, dargs) File "/usr/local/autotest/common_lib/test.py", line 380, in _call_run_once self.run_once(*args, **dargs) File "/usr/local/autotest/tests/graphics_dEQP/graphics_dEQP.py", line 607, in run_once (self._gpu_type, test_failures, test_count)) TestFail: Failed: on skylake 2/6 tests failed. ...
,
Mar 8 2017
,
Mar 8 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/60e6dc0b3698acfac1f6dfffff55f0f4557a4669 commit 60e6dc0b3698acfac1f6dfffff55f0f4557a4669 Author: Chad Versace <chadversary@chromium.org> Date: Wed Mar 08 23:19:16 2017 chipset-skl: Disable Vulkan Let's disable it on the release branches. Nothing uses it except dEQP tests, and there's no point in consuming testlab resources for something that's not used. BUG= chromium:699294 TEST=None Change-Id: Ic2dae6fe5de27245c0fc87d05c27ae17048d3aa1 Reviewed-on: https://chromium-review.googlesource.com/450875 Reviewed-by: Ilja H. Friedel <ihf@chromium.org> Commit-Queue: Chad Versace <chadversary@chromium.org> Tested-by: Chad Versace <chadversary@chromium.org> [modify] https://crrev.com/60e6dc0b3698acfac1f6dfffff55f0f4557a4669/chipset-skl/profiles/base/make.defaults
,
Mar 9 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/45640070cd123fb30335892720cdf35db9bbc923 commit 45640070cd123fb30335892720cdf35db9bbc923 Author: Chad Versace <chadversary@chromium.org> Date: Thu Mar 09 00:11:17 2017 chipset-apl: Disable Vulkan Let's disable it on the release branches. Nothing uses it except dEQP tests, and there's no point in consuming testlab resources for something that's not used. BUG= chromium:699294 TEST=None Change-Id: I2c19c8ac4d637b8d5abba53fbc485737ac4512de Reviewed-on: https://chromium-review.googlesource.com/451550 Reviewed-by: Ilja H. Friedel <ihf@chromium.org> Tested-by: Chad Versace <chadversary@chromium.org> [modify] https://crrev.com/45640070cd123fb30335892720cdf35db9bbc923/chipset-apl/profiles/base/make.defaults
,
Mar 9 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/45640070cd123fb30335892720cdf35db9bbc923 commit 45640070cd123fb30335892720cdf35db9bbc923 Author: Chad Versace <chadversary@chromium.org> Date: Thu Mar 09 00:11:17 2017 chipset-apl: Disable Vulkan Let's disable it on the release branches. Nothing uses it except dEQP tests, and there's no point in consuming testlab resources for something that's not used. BUG= chromium:699294 TEST=None Change-Id: I2c19c8ac4d637b8d5abba53fbc485737ac4512de Reviewed-on: https://chromium-review.googlesource.com/451550 Reviewed-by: Ilja H. Friedel <ihf@chromium.org> Tested-by: Chad Versace <chadversary@chromium.org> [modify] https://crrev.com/45640070cd123fb30335892720cdf35db9bbc923/chipset-apl/profiles/base/make.defaults |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by chadversary@chromium.org
, Mar 8 2017Drop Priority, because this does not impact normal operation of the system. The only thing in R58 that uses Vulkan is dEQP. I've never seen this error before. graphics_dEQP:0567| {'ResourceError': 2, 'Pass': 4} Perhaps a concurrently running test is consuming too many resources. Or maybe the resource limits in the dEQP source code are too high. First diagnoistic step: I'll investigate the resource limits in the dEQP Vulkan source. The resource limits are hard-coded instead of queried at runtime. That hard-coding is going to cause problems eventually... and maybe SKL-Y is the tipping point.