Validations errors in the vsgheadless examples

[dov]

The vsgheadless example outputs validation errors when run with the -d flag.

How to reproduce

./vsgheadless -f 1 -d cube.stl 

The result

VUID-VkAttachmentDescription-finalLayout-parameter(ERROR / SPEC): msgNum: -797790976 - Validation Error: [ VUID-VkAttachmentDescription-finalLayout-parameter ] | MessageID = 0xd072ad00 | vkCreateRenderPass(): pCreateInfo->pAttachments[0].finalLayout (VK_IMAGE_LAYOUT_PRESENT_SRC_KHR) requires the extensions VK_KHR_swapchain.
The Vulkan spec states: finalLayout must be a valid VkImageLayout value (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkAttachmentDescription-finalLayout-parameter)
VUID-VkShaderModuleCreateInfo-pCode-08737(ERROR / SPEC): msgNum: -1520283006 - Validation Error: [ VUID-VkShaderModuleCreateInfo-pCode-08737 ] | MessageID = 0xa5625282 | vkCreateShaderModule(): pCreateInfo->pCode (spirv-val produced an error):
Expected Image to have the same type as Result Type Image
  %222 = OpSampledImage %221 %215 %219
The Vulkan spec states: If pCode is a pointer to SPIR-V code, pCode must adhere to the validation rules described by the Validation Rules within a Module section of the SPIR-V Environment appendix (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkShaderModuleCreateInfo-pCode-08737)
VUID-VkPipelineShaderStageCreateInfo-pSpecializationInfo-06849(ERROR / SPEC): msgNum: 1132206547 - Validation Error: [ VUID-VkPipelineShaderStageCreateInfo-pSpecializationInfo-06849 ] | MessageID = 0x437c19d3 | vkCreateGraphicsPipelines(): pCreateInfos[0].pStages[1] After specialization was applied, VkShaderModule 0x220000000022[] produces a spirv-val error (stage VK_SHADER_STAGE_FRAGMENT_BIT):
Expected Image to have the same type as Result Type Image
  %222 = OpSampledImage %221 %215 %219
The Vulkan spec states: If a shader module identifier is not specified, the shader code used by the pipeline must be valid as described by the Khronos SPIR-V Specification after applying the specializations provided in pSpecializationInfo, if any, and then converting all specialization constants into fixed constants (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkPipelineShaderStageCreateInfo-pSpecializationInfo-06849)
Frame 0
VUID-VkImageMemoryBarrier-oldLayout-parameter(ERROR / SPEC): msgNum: -1505816164 - Validation Error: [ VUID-VkImageMemoryBarrier-oldLayout-parameter ] | MessageID = 0xa63f119c | vkCmdPipelineBarrier(): pImageMemoryBarriers[1].oldLayout (VK_IMAGE_LAYOUT_PRESENT_SRC_KHR) requires the extensions VK_KHR_swapchain.
The Vulkan spec states: oldLayout must be a valid VkImageLayout value (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkImageMemoryBarrier-oldLayout-parameter)
VUID-VkImageMemoryBarrier-newLayout-parameter(ERROR / SPEC): msgNum: 1140172143 - Validation Error: [ VUID-VkImageMemoryBarrier-newLayout-parameter ] | MessageID = 0x43f5a56f | vkCmdPipelineBarrier(): pImageMemoryBarriers[1].newLayout (VK_IMAGE_LAYOUT_PRESENT_SRC_KHR) requires the extensions VK_KHR_swapchain.
The Vulkan spec states: newLayout must be a valid VkImageLayout value (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkImageMemoryBarrier-newLayout-parameter)

Test system:

• Intel based laptop with integrated graphics running Fedora Linux.