Fix semaphore creation in smoke tests
authorPeter Quayle <peter.quayle@imgtec.com>
Tue, 8 Oct 2019 16:35:04 +0000 (17:35 +0100)
committerAlexander Galazin <Alexander.Galazin@arm.com>
Fri, 11 Oct 2019 07:32:39 +0000 (03:32 -0400)
commit99fe41dcea5801eb41244a8ca151eba1cbc24303
tree18c8d7a74bcedb27d2e42eda1351b098a4f8a805
parent7b7ba4e018b44ed5b873552ad7177df9813501ab
Fix semaphore creation in smoke tests

The test was calling createSemaphore instead of createSemaphoreType,
meaning that the semaphoreType value would incorrectly be interpreted
as a VkSemaphoreCreateFlags.

Additionally, the VkTimelineSemaphoreSubmitInfo struct was not being
added into the pNext chain of the submits. This probably went unnoticed
because the first bug could cause the test to use binary semaphores
even if semaphoreType was TIMELINE.

Affects:

dEQP-VK.synchronization.smoke.binary_semaphores
dEQP-VK.synchronization.smoke.timeline_semaphores

Components: Vulkan

VK-GL-CTS issue: 2041

Change-Id: I6936013b7f5a7e25f4af1fb4776d4d7273243d7a
(cherry picked from commit a8238c0aa023c121f79f09c6565875e235292f27)
external/vulkancts/modules/vulkan/synchronization/vktSynchronizationSmokeTests.cpp