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

Automatically clean up containers after sigkill during testrun #83

Open
fredericbirke opened this issue Feb 15, 2021 · 1 comment
Open

Comments

@fredericbirke
Copy link
Contributor

Is your feature request related to a problem? Please describe.
When debugging a test case and killing the debug process, the containers are not cleaned up, but live forever.

Describe the solution you'd like
Java testcontainers has found a solution to this by spinning up a container, that kills other containers, after the test process got killed. Maybe you can find some inspiration in their approach:

testcontainers/testcontainers-java#545

@vladimir-kovalyuk
Copy link

vladimir-kovalyuk commented Jun 7, 2023

We need to have unique container name for the tests that run in parallel and exclusively use container's resource. In case we run tests in collection they are executed sequentially and we don't need unique container name. In this approach this problem would have simpler solution if Squadron allowed to override container's name with non-unique one. Unfortunately ContainerResourceBuilder does not provide us with the way to override the container name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants