Speedup tests by putting physical devices in a map#1752
Merged
Conversation
Requires extensive modifications to the tests since previously many tests accessed the physical device array directly.
|
CI Vulkan-Loader build queued with queue ID 502803. |
|
CI Vulkan-Loader build queued with queue ID 502820. |
|
CI Vulkan-Loader build # 3143 running. |
|
CI Vulkan-Loader build # 3143 passed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requires extensive modifications to the tests since previously many tests accessed the physical device array directly.
The CreateDevice.ConsecutiveCreate test on linux-arm was taking +180s, with this PR only takes ~20s. 6x isn't a bad uplift (even if it is because of some naive test framework code being the culprit).