Fix tests for VK_EXT_device_address_binding_report
authorMarcin Kantoch <marcin.kantoch@amd.com>
Thu, 1 Dec 2022 19:37:25 +0000 (20:37 +0100)
committerPiotr Byszewski <piotr.byszewski@mobica.com>
Mon, 13 Feb 2023 16:08:10 +0000 (16:08 +0000)
commit8d410e0c982ca526a9ffc0a3e2174c24506f393b
tree7cd3bb98011cd961bd6248653090261af0f9d090
parent4801a8c5289de9b8431093152b4f99c33633fbf7
Fix tests for VK_EXT_device_address_binding_report

Tests for VK_EXT_device_address_binding_report contain several issues:

1. BindingCallbackRecorder is storing references to objects that are destroyed
after API call
2. Validation of binding pairs is only matching the first pair, not going
thought the whole vector
3. VK_EXT_debug_utils extension is not enabled on the custom instance
4. VkDebugUtilsMessengerEXT is not being created by the test
5. The test uses logical device not created from the custom instance

VK-GL-CTS Issue: 4175

Components: Vulkan

Affects:
dEQP-VK.memory.address_binding_report.*

Change-Id: I3952ad89f5e94d62db9edca3a4aba4abdc6d43b8
external/vulkancts/modules/vulkan/memory/vktMemoryAddressBindingTests.cpp