-
Notifications
You must be signed in to change notification settings - Fork 243
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
Isolate Podman tests in namespaces #6499
Isolate Podman tests in namespaces #6499
Conversation
Skipping CI for Draft Pull Request. |
✅ Deploy Preview for odo-docusaurus-preview canceled.
|
8174628
to
e7987fa
Compare
Podman tests are not passing due to conflicting Devfile component names: https://github.com/redhat-developer/odo/actions/runs/3943370985/jobs/6748117484#step:5:359 /hold Blocked on #6504, which should fix this behavior. |
e7987fa
to
037f153
Compare
48b6e2a
to
1cdb02b
Compare
ea15db2
to
edf1d58
Compare
/hold cancel |
… tests This way, we could be able to run them in parallel on GitHub but sequentially (default) locally. This will still benefit us by reducing the time it takes to run such tests on GitHub. Meanwhile, we can look into the issues we have locally with parallelization. Note that it is still possible to run them locally in parallel via the PODMAN_EXEC_NODE env var.
edf1d58
to
66ed98f
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
/override Kubernetes-Integration-Tests/Kubernetes-Integration-Tests |
@feloy: Overrode contexts on behalf of feloy: Kubernetes-Integration-Tests/Kubernetes-Integration-Tests, OpenShift-Integration-tests/OpenShift-Integration-tests 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. |
/override ci/prow/v4.11-integration-e2e |
@feloy: Overrode contexts on behalf of feloy: 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:
Unblocks #6485 by isolating each Podman test under a dedicated namespace. See #6485 (comment)
Note that even with isolated namespaces, two Podman containers cannot have the same name (I guess they share the same underlying
storage.conf
). So #6504 made sure to use random component names in our tests.PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer:
With proper isolation, we can run those Podman tests in parallel. This is the tentative done in
66ed98f
(#6499), which works well on GitHub Actions (up to a certain number of parallel nodes), but used to fail locally.