Skip to content

tests: Allow valid Timeout result - #13154

Closed
spencer-lunarg wants to merge 1 commit into
KhronosGroup:mainfrom
spencer-lunarg:spencer-lunarg-device-timeout-SKIP-CI
Closed

spencer-lunarg wants to merge 1 commit into
KhronosGroup:mainfrom
spencer-lunarg:spencer-lunarg-device-timeout-SKIP-CI

Conversation

@spencer-lunarg

Copy link
Copy Markdown
Contributor

RADV returns VK_TIMEOUT which is valid

@spencer-lunarg
spencer-lunarg requested a review from a team as a code owner September 18, 2026 16:46
@ci-tester-lunarg

Copy link
Copy Markdown
Collaborator

CI Vulkan-ValidationLayers build queued with queue ID 124377.

@ci-tester-lunarg

Copy link
Copy Markdown
Collaborator

CI Vulkan-ValidationLayers build # 24563 running.

uint32_t fault_counts = 0;
VkResult result = vk::GetDeviceFaultReportsKHR(device(), 0, &fault_counts, nullptr);
ASSERT_EQ(VK_SUCCESS, result);
ASSERT_TRUE(result == VK_TIMEOUT || result == VK_SUCCESS);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need this test then? it's called GetDeviceFaultReportsWithoutTimeout

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I need to talk with Samual again.... the whole ShaderAbort thing has been a disaster IMO, and seems a lack of testing/agreement how these device faults should work

... closing and going to figure this out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants