On Wed, 2 Oct 2024 10:23:05 GMT, Sebastian Lövdahl <d...@openjdk.org> wrote:
> However, when I'm running the test with `docker` with the changes from this > PR (`make test > TEST="jtreg:test/hotspot/jtreg/containers/docker/TestJcmdWithSideCar.java" > JTREG="JAVA_OPTIONS=-Djdk.test.container.command=docker"`) I get a new > failure: > [docker-failure.log](https://github.com/user-attachments/files/17227971/docker-failure.log). > If I revert the test runtime optimization (and keep the disabling part) the > test works with `docker` again. Thanks. Fails with: [main-container-process] docker: Error response from daemon: Conflict. The container name "/test-container-main" is already in use by container "258e8ebbbac586ffcc6a7703bcb977bd7b4c203f4badb2ab08e1651ee546c1d6". You have to remove (or rename) that container to be able to reuse that name. [main-container-process] See 'docker run --help'. java.lang.RuntimeException: Timed out while waiting for main() to start at TestJcmdWithSideCar$MainContainer.waitForMainMethodStart(TestJcmdWithSideCar.java:285) at TestJcmdWithSideCar.main(TestJcmdWithSideCar.java:110) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104) at java.base/java.lang.reflect.Method.invoke(Method.java:573) at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:333) at java.base/java.lang.Thread.run(Thread.java:1576) We'll have to do `docker rm -i /test-container-main` before we start a new one. I'll fix that later today. ------------- PR Comment: https://git.openjdk.org/jdk/pull/21289#issuecomment-2388475781
