Open ziga-lunarg opened 2 weeks ago
Running timeline semaphore tests in CTS reports UNASSIGNED-VkSemaphore-state-timeout and the message says This is most likely a validation bug.
UNASSIGNED-VkSemaphore-state-timeout
This is most likely a validation bug
One such test for example is dEQP-VK.synchronization.timeline_semaphore.device_host.write_copy_buffer_read_copy_buffer.buffer_16384
dEQP-VK.synchronization.timeline_semaphore.device_host.write_copy_buffer_read_copy_buffer.buffer_16384
And the full message is:
UNASSIGNED-VkSemaphore-state-timeout(ERROR / SPEC): msgNum: 1474714163 - Validation Error: [ UNASSIGNED-VkSemaphore-state-timeout ] Object 0: handle = 0x40b43c0000000049, type = VK_OBJECT_TYPESEMAPHORE; | MessageID = 0x57e65a33 | vkWaitSemaphores(): pWaitInfo->pValues[0] Timeout waiting for timeline semaphore state to update. This is most likely a validation bug. completed.payload=0 wait_payload=141 Objects: 1 [0] 0x40b43c0000000049, type: 5, name: NULL
There are other VUIDs that follow, but I assume they are caused by this first one.
I think this might be a test where many many semaphores a created and then it takes a very long time for them to be signaled. Possibly the timer for this error needs to be made longer.
Running timeline semaphore tests in CTS reports
UNASSIGNED-VkSemaphore-state-timeout
and the message saysThis is most likely a validation bug
.One such test for example is
dEQP-VK.synchronization.timeline_semaphore.device_host.write_copy_buffer_read_copy_buffer.buffer_16384
And the full message is:
There are other VUIDs that follow, but I assume they are caused by this first one.