-
Notifications
You must be signed in to change notification settings - Fork 244
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
Make sure to delete the component resources after each "delete component" test spec #6541
Conversation
…component" test spec Otherwise, "odo delete component --running-in $mode" might leave some resources running (on Podman especially). For example, the Podman test that runs "delete component --running-in deploy" (after starting and killing a Dev Session abruptly) might leave those Dev resources running. This has been alleviated in CI via 9ebf766 by ensuring Ginkgo does not hang indefinitely and by deleting those leftover resources. But the issue was still persisting locally.
✅ Deploy Preview for odo-docusaurus-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
/override ci/prow/v4.11-integration-e2e Flaky E2E test (reported in #6463) |
@rm3l: Overrode contexts on behalf of rm3l: ci/prow/v4.11-integration-e2e 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. |
What type of PR is this:
/kind tests
/area testing
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Otherwise, "odo delete component --running-in $mode" might leave some resources running
(on Podman especially).
For example, the Podman test that runs "delete component --running-in deploy"
(after starting and killing a Dev Session abruptly) might leave those Dev resources running.
This has been alleviated in CI via 9ebf766 by ensuring Ginkgo does not hang indefinitely and
by deleting those leftover resources.
But the issue was still persisting locally.
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer: