Hello, I have been using Jacoco for code coverage for both unit and integration test in the past. My env for integration test by then is pure docker image and it has been working great (using both tcpclient and destfile approaches). However, I encountered problems when I switched to kubernetes env, there, with tcpclient jvm option, I observed that .exec file (zero size) was created during the pod startup, then I ran the test, after that I used kubectl scale to shutdown the pod/container, .exec data wasn't flushed (from ExecutionDataServer), I also tried to kubectl exec to the container and issued kill command there to terminate the container's jvm, still no .exec flushed. One thing I noticed is that with docker env, visitSessionInfo method was called before flushing the data, however, this method was never get called for a container in a kubernetes env.
I'm not sure what additional info you prefer me to provide as this time, but I would happy to provide any info needed in order to investigate. Thanks! -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jacoco+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/748328d8-89a4-4526-a131-4fa87e0a426do%40googlegroups.com.
