Fix incorrect assumption for pipeline cache hit
authorArkadiusz Sarwa <arkadiusz.sarwa@amd.com>
Wed, 23 Oct 2019 15:15:12 +0000 (17:15 +0200)
committerArkadiusz Sarwa <arkadiusz.sarwa@amd.com>
Wed, 23 Oct 2019 15:23:49 +0000 (17:23 +0200)
The test incorrectly assumes that adding a pipeline creation flag bit
VK_PIPELINE_CREATE_ALLOW_DERIVATIVES_BIT to only one pipeline
still should cause a cache hit. Fixed the problem by adding the
VK_PIPELINE_CREATE_ALLOW_DERIVATIVES_BIT flag bit to both pipelines.

Affects:
dEQP-VK.pipeline.creation_feedback.compute_tests.compute_stage

Components: Vulkan
VK-GL-CTS issue: 2068

Change-Id: Idb963219a4e894eee6a0bb3b1fc20797d5b0323e

external/vulkancts/modules/vulkan/pipeline/vktPipelineCreationFeedbackTests.cpp

index 1344a90..6c116f3 100644 (file)
@@ -1113,7 +1113,7 @@ void ComputeCacheTestInstance::buildPipeline (deUint32 ndx)
                0u,                                                                                                                     // deInt32                                                      basePipelineIndex;
        };
 
-       if (ndx == PIPELINE_CACHE_NDX_NO_CACHE)
+       if (ndx != PIPELINE_CACHE_NDX_DERIVATIVE)
        {
                pipelineCreateInfo.flags = VK_PIPELINE_CREATE_ALLOW_DERIVATIVES_BIT;
        }