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

Don't rely on the '--rm' flag for stopping containers in integration tests #21119

Merged
merged 1 commit into from
Nov 1, 2021

Conversation

geoand
Copy link
Contributor

@geoand geoand commented Nov 1, 2021

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

@quarkus-bot
Copy link

quarkus-bot bot commented Nov 1, 2021

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building 09efd94

Status Name Step Failures Logs Raw logs
✔️ JVM Tests - JDK 11
JVM Tests - JDK 17 Build Failures Logs Raw logs
Native Tests - Windows - hibernate-validator Build Failures Logs Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 17 #

- Failing: integration-tests/vault-agroal 

📦 integration-tests/vault-agroal

io.quarkus.vault.AgroalVaultITCase. - More details - Source on GitHub

java.lang.RuntimeException: Error waiting for test resource future to finish.
	at io.quarkus.test.common.TestResourceManager.waitForAllFutures(TestResourceManager.java:151)
	at io.quarkus.test.common.TestResourceManager.start(TestResourceManager.java:136)

io.quarkus.vault.AgroalVaultKv1ITCase. - More details - Source on GitHub

java.lang.RuntimeException: Error waiting for test resource future to finish.
	at io.quarkus.test.common.TestResourceManager.waitForAllFutures(TestResourceManager.java:151)
	at io.quarkus.test.common.TestResourceManager.start(TestResourceManager.java:136)

io.quarkus.vault.VaultKv1ITCase. - More details - Source on GitHub

java.lang.RuntimeException: Error waiting for test resource future to finish.
	at io.quarkus.test.common.TestResourceManager.waitForAllFutures(TestResourceManager.java:151)
	at io.quarkus.test.common.TestResourceManager.start(TestResourceManager.java:136)

⚙️ Native Tests - Windows - hibernate-validator #

- Failing: integration-tests/hibernate-validator 

📦 integration-tests/hibernate-validator

Failed to execute goal io.quarkus:quarkus-maven-plugin:999-SNAPSHOT:build (default) on project quarkus-integration-test-hibernate-validator: Failed to build quarkus application

@geoand geoand requested a review from gastaldi November 1, 2021 15:51
…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
@geoand geoand added the triage/waiting-for-ci Ready to merge when CI successfully finishes label Nov 1, 2021
@gastaldi gastaldi merged commit 508e2fa into quarkusio:main Nov 1, 2021
@gastaldi gastaldi deleted the #21101 branch November 1, 2021 23:58
@quarkus-bot quarkus-bot bot added this to the 2.5 - main milestone Nov 1, 2021
@quarkus-bot quarkus-bot bot removed the triage/waiting-for-ci Ready to merge when CI successfully finishes label Nov 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Docker container is not stopped (on Windows) after integration test
3 participants