Replies: 4 comments 1 reply
-
Which test is affected? |
Beta Was this translation helpful? Give feedback.
-
My tests, not Trino's own tests.
Therefore, it will check my containers also, and I'm happy about it, just there's a scenario where exposed host port to the docker network is implemented with an sshd (testcontainers/sshd:1.1.0) internally, and that triggers the JVM kill ( I haven't found a nicer approach yet to handle this situation, so I'm using |
Beta Was this translation helpful? Give feedback.
-
since you use trino-testing-containers, including |
Beta Was this translation helpful? Give feedback.
-
I'm also having the similar issue here, any update to this? @durban77 @findepi
|
Beta Was this translation helpful? Give feedback.
-
When you expose a port to the network in testing with
org.testcontainers.Testcontainers#exposeHostPorts(int...)
It starts a
testcontainers/sshd
in the docker session as can be seen inorg.testcontainers.containers.PortForwardingContainer
.After the tests complete, the new
testing/trino-testing-containers/src/main/java/io/trino/testing/containers/junit/ReportLeakedContainers.java
's check will crash the JVM.I think that ReportLeakedContainers should ignore the sshd, as it is out of scope for this check.
Beta Was this translation helpful? Give feedback.
All reactions