Fix TestCheckAccessToRegisteredResource flaky test#24118
Closed
Fix TestCheckAccessToRegisteredResource flaky test#24118
TestCheckAccessToRegisteredResource flaky test#24118Conversation
When multiple tests run in parallel and one of them replaces the module's features, it affects all the running tests. A test was changing the modules while running in parallel and it resulted in the flakiness of `TestCheckAccessToRegisteredResource` because, since #23755, we enforce that the server has the Kubernetes feature enabled in order to upsert the server. Fixes #24115
Contributor
Author
|
Closing in favor of #24117 that also fixes this issue |
Merged
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
1 participant
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.
When multiple tests run in parallel and one of them replaces the module's features, it affects all the running tests.
A test was changing the modules while running in parallel and it resulted in the flakiness of
TestCheckAccessToRegisteredResourcebecause, since #23755, we enforce that the server has the Kubernetes feature enabled in order to upsert the server.Fixes #24115