You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the supervisor uses podman stop to stop containers. This means that they (rarely) survive the close attempt. The supervisor should give them no choice and use podman kill to destroy the processes.
This sometimes results in:
java.io.IOException: Container process Process[pid=3558105, exitValue="not exited"] is still alive!
at [email protected]/com.io7m.ervilla.native_exec.internal.EContainerSupervisor$EContainer.stop(EContainerSupervisor.java:919)
at [email protected]/com.io7m.northpike.tests.containers.NPTestContainers$NPIdstoreFixture.reset(NPTestContainers.java:269)
at [email protected]/com.io7m.northpike.tests.user_client.NPUserClientTest.setup(NPUserClientTest.java:142)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
The text was updated successfully, but these errors were encountered:
The method used to stop containers is now configurable. STOP is the old
"podman stop" method. KILL allows for the use of "podman kill". This
may avoid any container surviving a test execution.
Affects: #2
Currently, the supervisor uses
podman stop
to stop containers. This means that they (rarely) survive the close attempt. The supervisor should give them no choice and usepodman kill
to destroy the processes.This sometimes results in:
The text was updated successfully, but these errors were encountered: