-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Don't rely on the '--rm' flag for stopping containers in integration tests #21119
Conversation
test-framework/common/src/main/java/io/quarkus/test/common/DefaultDockerContainerLauncher.java
Show resolved
Hide resolved
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building 09efd94
Full information is available in the Build summary check run. Failures⚙️ JVM Tests - JDK 17 #- Failing: integration-tests/vault-agroal
📦 integration-tests/vault-agroal✖
✖
✖
⚙️ Native Tests - Windows - hibernate-validator #- Failing: integration-tests/hibernate-validator
📦 integration-tests/hibernate-validator✖ |
test-framework/common/src/main/java/io/quarkus/test/common/DefaultDockerContainerLauncher.java
Outdated
Show resolved
Hide resolved
test-framework/common/src/main/java/io/quarkus/test/common/DefaultDockerContainerLauncher.java
Outdated
Show resolved
Hide resolved
…tests It seems that this flag is not very reliable on some cases in Windows, so we just give the container a name and use that name to manually stop the container. Fixes: quarkusio#21101
It seems that this flag is not very reliable on some cases in Windows,
so we just give the container a name and use that name to manually
stop the container.
Fixes: #21101