POstgres service not getting killed for imporper shutdown of test case

[alexsander55]

While running the test case , when the springboot test is shutdown forcefully in windows , the postgres intance that started is not getting killed.

version of embedded-database-spring-test used is 1.5.4
Window machine

[tomix26]

Thanks for the report. I'll try to look at it, but I'm afraid there's not much that can be done about it. Because a shutdown hook is already registered every time a new postgres process is started, and as you can see, that's not enough.

Javadoc describing the behavior of shutdown hooks:

In rare circumstances the virtual machine may abort, that is, stop running without shutting down cleanly. This occurs when the virtual machine is terminated externally, for example with the SIGKILL signal on Unix or the TerminateProcess call on Microsoft Windows. The virtual machine may also abort if a native method goes awry by, for example, corrupting internal data structures or attempting to access nonexistent memory. If the virtual machine aborts then no guarantee can be made about whether or not any shutdown hooks will be run.

[AndreKoepke]

I have the same problem with Testcontainer databases. They run forever.

[tomix26]

I have the same problem with Testcontainer databases. They run forever.

If you are using the Docker provider, the Testcontainers library should take care of cleaning up the database containers itself. It uses a helper Ryuk container for this purpose. Please make sure you haven't disabled this functionality - https://java.testcontainers.org/features/configuration/#disabling-ryuk

[AndreKoepke]

It seems to be a local problem for me. In my case (MacBook M4 with Podman), the Ryuk-container behaves correcty, but the Postgres-Containers not.

In my team, I'm the only one with that problem. I would then just decline my PR here. :)
Thanks for the help. 👍

[tomix26]

It seems to be a local problem for me. In my case (MacBook M4 with Podman), the Ryuk-container behaves correcty, but the Postgres-Containers not.

In my team, I'm the only one with that problem. I would then just decline my PR here. :) Thanks for the help. 👍

The problem might be caused by using Podman. Testcontainers should support it, but I've never tried it myself. So I'm not sure if the library is fully compatible. If you figure out what's causing the issue and it's something I can fix, let me know.

[AndreKoepke]

A colleague has also a MacBook (M1) with Podman. And for him, it works correctly. Funny thing.