Ricardo Garcia

I'd guess devices supporting non constant indices will "handle the situation" no matter if the capability is requested by the shader or not, so checking for the feature being available...

NotSupported typically means that the test requires a feature which is not available, so it can't run.

A fix for this is under review in Khronos. It renames the CTS "build" package to "ctsbuild" to avoid name conflicts.

@mgorchak-blackberry could you please check the following fix for the main branch? ```diff diff --git a/external/vulkancts/modules/vulkan/api/vktApiDeviceDrmPropertiesTests.cpp b/external/vulkancts/modules/vulkan/api/vktApiDeviceDrmPropertiesTests.cpp index 3222a51df..77b6d650e 100644 --- a/external/vulkancts/modules/vulkan/api/vktApiDeviceDrmPropertiesTests.cpp +++ b/external/vulkancts/modules/vulkan/api/vktApiDeviceDrmPropertiesTests.cpp @@ -74,7 +74,7 @@ void testFilesExist...

This was solved in f37acc26a452000151963eafe07625d858a4f3f5, IIRC.

After 9d40bd7aee42a6dbe7da8e348d8582217917ae55 you can use -DGLES_ALLOW_DIRECT_LINK=0 when configuring CTS, which forces GLES symbols to be loaded dynamically.

Yes, I think so. I wanted to get my foot in the door first with the change above. I'll keep this issue open to propose another change in the future...

Ah, yes. :facepalm: I'll propose a cherry-pick to the 4.6.3 branch. By the way, the change to make it the default behavior is currently under review (also for main, will...

The new behavior has been made default in main with d37edb1a141fd1da0dd74c3c12f8612732057c9a. @kusma can you confirm this fixes the issue for you by default with no drawbacks?

No problem! The change to make this the default behavior has not been backported to any release branch. What about submitting a cherry-pick for 4.6.3 and then closing the issue?