After adding support for VK_KHR_portability_subset
and executing CTS on MoltenVK some issues surfaced.
They are beeing resolved in a series of small CLs.
This change checks if VK_KHR_portability_subset is
available in ycbcr query tests (some of those tests
require tessellation isolines which are under feature
flag in portability).
See:
https://github.com/KhronosGroup/MoltenVK/issues/1285
Components: Vulkan
Affects:
dEQP-VK.ycbcr.query.*
Change-Id: I02e68718af4b7cdb0778890e231ad559e52ac19a
if (isYCbCrImage)
checkImageSupport(context, params.format, params.flags);
+
+ checkSupportShader(context, params.shaderType);
}
tcu::TestStatus testImageQueryLod (Context& context, TestParameters params)
VK_KHR_deferred_host_operations DEVICE
VK_KHR_fragment_shading_rate DEVICE
VK_KHR_zero_initialize_workgroup_memory DEVICE
-VK_KHR_workgroup_memory_explicit_layout DEVICE
+VK_KHR_workgroup_memory_explicit_layout DEVICE
VK_KHR_synchronization2 DEVICE
VK_EXT_color_write_enable DEVICE