CTS Fails tests when returning XR_ERROR_FEATURE_UNSUPPORTED in CreateSwapchain for flag "XR_SWAPCHAIN_CREATE_STATIC_IMAGE_BIT"

[JetSimon]

Hello,

In the OpenXR specificiation it says we can return XR_ERROR_FEATURE_UNSUPPORTED if a createFlag is unsupported. However when I return XR_ERROR_FEATURE_UNSUPPORTED I get this error from the testing suite when running any test to do with swapchains.

   <testcase classname="global" name="MaxLayers-noninteractive" time="0.000" status="run">
      <error message="{Unknown expression after the reported line}">
FAILED:
  {Unknown expression after the reported line}
XrResult failure [XR_ERROR_FEATURE_UNSUPPORTED]
    Origin: xrCreateSwapchain(m_session, &amp;createInfo, &amp;swapchain)
    Source: D:\HololabsGitRepos\OpenXR-CTS\src\conformance\framework\composition_utils.cpp:621
at D:\HololabsGitRepos\OpenXR-CTS\src\conformance\framework\conformance_utils.cpp(137)
      </error>
    </testcase>

This is how I am checking for the flag, which I believe is correct:

if (createInfo->createFlags & XR_SWAPCHAIN_CREATE_STATIC_IMAGE_BIT) {
	return XR_ERROR_FEATURE_UNSUPPORTED;
}

I'm not sure why I cannot pass the test if I report this feature unsupported?

As per the spec:

A runtime may implement any of these, but is not required to. A runtime must return XR_ERROR_FEATURE_UNSUPPORTED from xrCreateSwapchain if an XrSwapchainCreateFlags bit is requested but not implemented.

[rpavlik]

The "implementation of flags is optional" was mainly meant for the protected content bit. If you can't support static swapchains (which are just swapchains with one image, that are populated only once), you'll need to make a lot of CTS changes in order to compensate for that, and you will probably find many applications do not run.

[JetSimon]

Okay, so I should implement that because it isn't really optional. Thanks!

[rpavlik-bot]

An issue (number 2768) has been filed to correspond to this issue in the internal Khronos GitLab (Khronos members only: KHR:openxr/openxr#2768 ), to facilitate working group processes.

This GitHub issue will continue to be the main site of discussion.