-
Notifications
You must be signed in to change notification settings - Fork 393
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
Test suite crashes #7893
Comments
OBS causes this issue. There is this documentation section: https://github.com/KhronosGroup/Vulkan-ValidationLayers/tree/main/tests#implicit-layers-note Maybe this can be categorized as this issue #3681 (@spencer-lunarg ) I also have problem with OBS locally, and usually use this brute force solution (notice the underscore to disable layer), but I guess the best practice is to use the method from documentation: |
So for windows: Linux/MacOS As for the tests setting these by themselves, its possible but doesn't work on older loaders (so only loaders 1.3.234 and newer will respect the environment variable). |
@charles-lunarg is there a way for the app (in this case the VVL test app) to do the |
If you mean through the Vulkan API, there is not one as far as I know. However, it is not difficult to set environment variables. I recently made validation set VK_LAYER_PATH if it wasn't set already. It'd be trivial to set VK_LOADER_LAYERS_DISABLE= |
In my own apps i do something like this before i start using vulkan, copy it as you please
|
Environment:
Describe the Issue
I'm trying to run the testsuite according to these steps:
#7891 (comment)
It mostly works fine up until about 30 tests in. Then it crashes inside
TEST_F(VkBestPracticesLayerTest, UseDeprecatedInstanceExtensions)
The loader jumps through graphics-hook64 (i think obs?) and then crashes in RTSSVkLayer64 (riva tuner statistics server, shipped with MSI Afterburner)
Expected behavior
The testsuite protects itself against faulty implicit layers. For example with the VK_LOADER_LAYERS_DISABLE + VK_LOADER_LAYERS_ENABLE combination.
The text was updated successfully, but these errors were encountered: