Skip to content
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

Merged
merged 1 commit into from Apr 2, 2024

Conversation

alexzielenski
Copy link
Contributor

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?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. kind/bug Categorizes issue or PR as related to a bug. labels Mar 21, 2024
@k8s-ci-robot k8s-ci-robot added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/flake Categorizes issue or PR as related to a flaky test. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 21, 2024
@Jefftree
Copy link
Member

/triage accepted
/assign @jpbetz
/lgtm

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 21, 2024
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: d0560d45fd95567094cc79060062fc5a795680af

@bart0sh bart0sh added this to Triage in SIG Node CI/Test Board Mar 24, 2024
@pacoxu
Copy link
Member

pacoxu commented Mar 26, 2024

/assign @jiahuif @liggitt @deads2k
Does this need to be included in v1.30?

@liggitt
Copy link
Member

liggitt commented Mar 29, 2024

/assign @jiahuif @liggitt @deads2k Does this need to be included in v1.30?

probably... this looks to be the flakiest integration test we have currently

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 29, 2024
@alexzielenski
Copy link
Contributor Author

feedback addressed

@bart0sh bart0sh moved this from Triage to Archive-it in SIG Node CI/Test Board Mar 31, 2024
@pacoxu
Copy link
Member

pacoxu commented Apr 1, 2024

/assign @jiahuif @liggitt @deads2k Does this need to be included in v1.30?

probably... this looks to be the flakiest integration test we have currently

Yes. This flake ~ once a day in https://testgrid.k8s.io/sig-release-master-blocking#integration-master.

@liggitt
Copy link
Member

liggitt commented Apr 2, 2024

/lgtm
/approve
/milestone v1.30

test-only fix for the flakiest integration test we currently have

@k8s-ci-robot k8s-ci-robot added this to the v1.30 milestone Apr 2, 2024
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 2, 2024
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: c8643e0c4398b5864210fdb9c78bb089d8ff56a0

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 2, 2024
@k8s-ci-robot k8s-ci-robot merged commit c9f6d4e into kubernetes:master Apr 2, 2024
14 checks passed
SIG Node CI/Test Board automation moved this from Archive-it to Done Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/flake Categorizes issue or PR as related to a flaky test. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Development

Successfully merging this pull request may close these issues.

[Flaking Test] master-integration TestRatchetingFunctionality
8 participants