-
Notifications
You must be signed in to change notification settings - Fork 3.4k
test: Avoid using global map for Cilium configuration #10388
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
Conversation
The same instance of the configuration map is shared among the tests. So, any modification to the map might unintentionally influence non-related test case. Signed-off-by: Martynas Pumputis <m@lambda.lt>
Release note label not set, please set the appropriate release note. |
4 similar comments
Release note label not set, please set the appropriate release note. |
Release note label not set, please set the appropriate release note. |
Release note label not set, please set the appropriate release note. |
Release note label not set, please set the appropriate release note. |
test-me-please |
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.
Seems not ideal, and safe to merge of course, though I think ginkgo gives us a guarantee that the tests will be run in order so I don't think this makes a practical difference for current tests?
Still it's bad style so good idea to merge. Not sure it makes a difference for backport.
The same instance of the configuration map is shared among the tests. So, any modification to the map might unintentionally influence a non-related test case.
This change is