-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Functions in testutil are commented out #386
Comments
I'm not even sure why they're still there -- they should be removed. For tests, the recommendation is just to do |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten we should remove that file |
/help |
@vincepri: Please ensure the request meets the requirements listed here. 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. |
commits remove the testutil.go file which is commented and no longer required. fixes:kubernetes-sigs#386 Signed-off-by: prateekpandey14 <[email protected]>
I would like to disable the client caching in some of my tests as it doesn't always seem to reflect the latest resource changes and it really gets in the way.
If I use a new client I can see the latest changes as expected so I assume it's a caching thing. But If I use a different client from the one that the test manager uses, they will always be unsynced, so it's still a caching problem.
It seemed like these functions might help me in disabling the cache, although I'm not sure it's possible. Any clue why they are commented?
The text was updated successfully, but these errors were encountered: