Remove vkDestroyBuffer
authorAri Suonpaa <ari.suonpaa@siru.fi>
Tue, 14 Dec 2021 05:27:53 +0000 (07:27 +0200)
committerMatthew Netsch <quic_mnetsch@quicinc.com>
Thu, 6 Jan 2022 22:40:40 +0000 (22:40 +0000)
A buffer allocation test that is supposed to fail a large
allocation still tried to destroy the buffer even when an
error was returned from the allocation. This is now removed.

VK-GL-CTS Issue: 3192

Affects:

dEQP-VK.api.buffer.basic.size_max_uint64

Components: Vulkan
Change-Id: Ic36cb548ab2796b41e2a0b44d023e644b02a6d8c

external/vulkancts/modules/vulkan/api/vktApiBufferTests.cpp

index 97cf062..fb314f4 100644 (file)
@@ -691,8 +691,6 @@ tcu::TestStatus testOverlyLargeBuffer(Context& context, deUint64 bufferSize)
                return tcu::TestStatus::fail("Fail");
        }
 
-       vk.destroyBuffer(vkDevice, rawBuffer, DE_NULL);
-
        // check if one of the allowed errors was returned
        if ((result == VK_ERROR_OUT_OF_DEVICE_MEMORY) ||
                (result == VK_ERROR_OUT_OF_HOST_MEMORY))