-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
TestPatch is flaky #8478
Comments
/triage accepted |
/help |
@killianmuldoon: 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. |
Example:
Permalink to check occurence. Reproducible (not 100%) locally using: export KUBEBUILDER_ASSETS=/path/to/my/kubebuilder-arm64-1.28.0
go test -race -count 120 -failfast -shuffle on -timeout 30s -run '^TestPatch$' sigs.k8s.io/cluster-api/internal/util/ssa |
First analysis: cluster-api/internal/util/ssa/patch.go Line 104 in 235d965
seems to patch the object again. |
Maybe related: kubernetes/kubernetes#118519 |
Which jobs are flaking?
Unit test runs on 1.4 and main.
Which tests are flaking?
sigs.k8s.io/cluster-api/internal/util/ssa.TestPatch
Since when has it been flaking?
This test has been flaking since it was introduced.
Testgrid link
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/periodic-cluster-api-test-release-1-4/1640193879221211136
Reason for failure (if possible)
I did a little bit of debugging on this one and found that sometimes the resourceVersion of the object being patched (but only for the MachineTests in my reproduction) is bumped along with the time signature in the managed fields, but there is no other change on the object.
This results in the ssa call not being cached, as it checks the resourceVersion, unexpectedly.
Anything else we need to know?
No response
Label(s) to be applied
/kind flake
/area testing
The text was updated successfully, but these errors were encountered: