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
fix test flake caused by not waiting for CRD schema update #124019
fix test flake caused by not waiting for CRD schema update #124019
Conversation
/triage accepted |
LGTM label has been added. Git tree hash: d0560d45fd95567094cc79060062fc5a795680af
|
staging/src/k8s.io/apiextensions-apiserver/test/integration/ratcheting_test.go
Show resolved
Hide resolved
staging/src/k8s.io/apiextensions-apiserver/test/integration/ratcheting_test.go
Outdated
Show resolved
Hide resolved
staging/src/k8s.io/apiextensions-apiserver/test/integration/ratcheting_test.go
Outdated
Show resolved
Hide resolved
a2df5d8
to
a7933dc
Compare
feedback addressed |
a7933dc
to
0add741
Compare
Yes. This flake ~ once a day in https://testgrid.k8s.io/sig-release-master-blocking#integration-master. |
/lgtm test-only fix for the flakiest integration test we currently have |
LGTM label has been added. Git tree hash: c8643e0c4398b5864210fdb9c78bb089d8ff56a0
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexzielenski, liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind bug
/kind failing-test
/kind flake
What this PR does / why we need it:
Fixes a flake in some test code. Flake was caused by our check to make sure CRD schema was updated. We would check to see a returned error had special string, but the error message would unconditionally contain the string since we had used within the send value, so we never would actually wait....I'm surprised it did not flake more than it had.
FIxed by no longer sending the special string in with the object, and instead encoding the special string as a custom CEL error message. This is a better way of checking that the new schema is being updated.
Which issue(s) this PR fixes:
Fixes #123854
Special notes for your reviewer:
/assign @Jefftree
/cc @pacoxu
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: