Avoid exceeding maxPerStageResources in descriptor_indexing tests
authorSlawomir Cygan <slawomir.cygan@intel.com>
Mon, 27 Apr 2020 13:14:42 +0000 (15:14 +0200)
committerAlexander Galazin <Alexander.Galazin@arm.com>
Fri, 8 May 2020 15:23:14 +0000 (11:23 -0400)
commitfc9f58142d09c2a796a4134d3eb496f69aa35bb8
tree3a190e963370489c97d2536aee8c926086fc3b9a
parent9045a04e762a698345f862358fe7ce538a9f75b7
Avoid exceeding maxPerStageResources in descriptor_indexing tests

The 'calculateInLoop; (*_in_loop) variant of the test is using additional
uniform texel buffer descriptor binding in pipeline layout.

This binding was counted only against maxPerStageDescriptorSampledImages and
maxDescriptorSetSampledImages limits, but not maxPerStageResources.

The fix is to count it against all three limits - but do this only when needed (in
*_in_loop) tests.

Component: Vulkan

VK-GL-CTS Issue: 2333

Affects: dEQP-VK.descriptor_indexing.*

Change-Id: I1c3476cb8c50c3ed61e73ecd4c106e6e9b613022
external/vulkancts/modules/vulkan/descriptor_indexing/vktDescriptorSetsIndexingTests.cpp
external/vulkancts/modules/vulkan/descriptor_indexing/vktDescriptorSetsIndexingTests.hpp
external/vulkancts/modules/vulkan/descriptor_indexing/vktDescriptorSetsIndexingTestsUtils.cpp