Thank you. I figured out the issue. It wasn't really parallel vs sequential issue. I was running jmockit for unit test and that coverage wasn't included in the jacoco report because I was on jacoco version 0.7.9, the issue described in https://github.com/jmockit/jmockit1/issues/125 . After i switched to 0.8.0 the jmockit unit test coverage was also accounted for.
On Monday, January 15, 2018 at 6:27:18 AM UTC-5, Evgeny Mandrikov wrote: > > > > On Sunday, January 14, 2018 at 6:12:41 PM UTC+1, Causalbody wrote: >> >> Hi Guys, >> I am seeing significant variations in jacoco coverage report for the same >> set of integration tests run in "parallel" vs "sequential". > > > As far as we know and according to our tests JaCoCo perfectly works in > case of parallel execution of tests. > > IMO the only advices that can be given in absence of *complete* runnable > *reproducer*: > > - make sure that behavior of your tests is deterministic and that your > own components do not have concurrency problems > - JaCoCo writes execution data from JVM shutdown hook, so make sure > that your JVM(s) terminate gracefully and that shutdown hooks are > executed, > in particular that you don't leave main threads in interrupted state - see > https://bugs.openjdk.java.net/browse/JDK-8154017 > > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/7839a658-79d8-435d-a4fd-551df1450416%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
