KhronosGroup / KhronosGroup/OpenCL-CTS
test_vulkan: VVL error VUID-vkImportSemaphoreFdKHR-semaphore-01142
- Dominant language
- C++
- Stars
- 232
- Forks
- 235
- Avg merge
- 8d 7h
- Merged PRs (30d)
- 18
Description
> Validation Error: [ VUID-vkImportSemaphoreFdKHR-semaphore-01142 ] | MessageID = 0x668a54af
vkImportSemaphoreFdKHR(): pImportSemaphoreFdInfo->semaphore can't be called on VkSemaphore 0xb000000000b that is currently in use by VkQueue 0x3959fbc0.
The Vulkan spec states: semaphore must not be associated with any queue command that has not yet completed execution on that queue (https://docs.vulkan.org/spec/latest/chapters/synchronization.html#VUID-vkImportSemaphoreFdKHR-semaphore-01142)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the test_vulkan case and reproduce the reported VVL error for vkImportSemaphoreFdKHR, using the Vulkan synchronization specification link in the issue. Trace why the semaphore is still associated with VkQueue when the import is called; done means the test no longer produces VUID-vkImportSemaphoreFdKHR-semaphore-01142.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100