-
Notifications
You must be signed in to change notification settings - Fork 410
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests: Disable message limit in tests #9036
base: main
Are you sure you want to change the base?
tests: Disable message limit in tests #9036
Conversation
CI Vulkan-ValidationLayers build queued with queue ID 325549. |
CI Vulkan-ValidationLayers build # 18342 running. |
CI Vulkan-ValidationLayers build # 18342 failed. |
5dec776
to
74a41a3
Compare
CI Vulkan-ValidationLayers build queued with queue ID 325577. |
CI Vulkan-ValidationLayers build # 18343 running. |
CI Vulkan-ValidationLayers build # 18343 passed. |
@@ -320,6 +320,16 @@ VkSamplerCreateInfo SafeSaneSamplerCreateInfo() { | |||
} | |||
|
|||
void VkLayerTest::Init(VkPhysicalDeviceFeatures *features, VkPhysicalDeviceFeatures2 *features2, void *instance_pnext) { | |||
const VkBool32 enable_message_limit = false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
putting it in here seems like a great way for people to get burned if they go
RETURN_IF_SKIP(InitFramework(something_else));
RETURN_IF_SKIP(InitState());
I also created a static VkLayerSettingsCreateInfoEXT kDisableMessageLimit
that can be used here
74a41a3
to
f9d16dd
Compare
CI Vulkan-ValidationLayers build queued with queue ID 325898. |
CI Vulkan-ValidationLayers build # 18352 running. |
CI Vulkan-ValidationLayers build # 18352 passed. |
The message limit should be disabled in the tests by default. Some tests are currently failing when reaching this limit.