Includes config param to limit the amount of different instance configs tested#972
Merged
Includes config param to limit the amount of different instance configs tested#972
Conversation
configurations tested
rjschwei
approved these changes
Feb 27, 2026
smarlowucf
reviewed
Mar 2, 2026
smarlowucf
approved these changes
Mar 2, 2026
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
3 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.
configurations tested
What does this PR do? Why are we making this change?
With images supporting some cloud instance configuration features running all the tests in all the feature combinations can result in a big number of instance configurations tested.
This PR includes a new config param to limit the amount of different instances for the tests. The tests run are a random subset of all the combinations of features supported by the instance.
How will these changes be tested?
These will be tested in a mash instance.
How will this change be deployed? Any special considerations?
Additional Information