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.

Sign up for GitHub

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

Jump to bottom

Flaky tests because of CRD deletion #2728

Closed
csviri opened this issue Mar 10, 2025 · 1 comment · Fixed by #2729
Closed

Flaky tests because of CRD deletion #2728

csviri opened this issue Mar 10, 2025 · 1 comment · Fixed by #2729

Comments

@csviri
Copy link
Collaborator

csviri commented Mar 10, 2025

Quite often see this error:
https://github.com/operator-framework/java-operator-sdk/actions/runs/13768182946/job/38499882350?pr=2722

Usually for E2E tests. Would be nice to make CRD deletion feature more robust. (Or opt in for the e2e tests)
@csviri
Copy link
Collaborator Author

csviri commented Mar 10, 2025 •
edited
Loading

@xstefank I was thinking that if the CRD is not deleted or we cannot delete with a timeout it could be just a warning in the logs (so we delete it with kinda best effort, but don't fail the tests because of that). WDYT?

@xstefank xstefank mentioned this issue Mar 10, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: don't fail test if the CRD cannot be deleted xstefank/java-operator-sdk
1 participant
@csviri