Enable VK_KHR_ray_tracing_pipeline only if needed
authorRicardo Garcia <rgarcia@igalia.com>
Fri, 30 Oct 2020 15:10:43 +0000 (16:10 +0100)
committerAlexander Galazin <Alexander.Galazin@arm.com>
Thu, 3 Dec 2020 18:35:12 +0000 (13:35 -0500)
commite5735c76c5eb51133a6c3b7763f8556cd868bfbb
tree2443e49e381eb86eac1d1f0225059d0233e533a2
parent756a198f6f3f5aa63a8b10c3c5fe4cf60fb3b2bb
Enable VK_KHR_ray_tracing_pipeline only if needed

This commit makes the default test device not enable the
VK_KHR_pipeline_library extension by default, which can potentially affect all
ray tracing and ray query tests.

Ray tracing pipeline tests are modified to use a custom device with the needed
features enabled, including the VK_KHR_pipeline_library extension. The tests
also check the extension is supported if VK_KHR_ray_tracing_pipeline is
supported, failing the test early if not.

Modified tests:
dEQP-VK.ray_tracing_pipeline.pipeline_library.*

Affected tests:
dEQP-VK.ray_tracing_pipeline.*
dEQP-VK.ray_query.*

Components: Vulkan
VK-GL-CTS issue: 2592

Change-Id: I1494ab3ce28fdce892f0444cba9ca538caec1208
external/vulkancts/modules/vulkan/api/vktApiFeatureInfo.cpp
external/vulkancts/modules/vulkan/ray_tracing/vktRayTracingPipelineLibraryTests.cpp
external/vulkancts/modules/vulkan/vktTestCase.cpp