-
Notifications
You must be signed in to change notification settings - Fork 336
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
Is not working utilfeaturetesting.SetFeatureGateDuringTest for TestProvisionFromPVC Parallel Test #833
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
@msau42: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/triage accepted |
/assign |
This issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
What happened:
Is not working utilfeaturetesting.SetFeatureGateDuringTest for TestProvisionFromPVC Parallel Test .
What you expected to happen:
DefaultFeatureGate defined in utilfeature seems a global value, therefore setting value during tests causes changes to a global value in each test.
How to reproduce it:
execute TestProvisionFromPVC Parallel Test in the state of enabling utilfeaturetesting.SetFeatureGateDuringTest
Anything else we need to know?:
#805 (comment)
Environment:
The text was updated successfully, but these errors were encountered: