On Monday, May 6, 2019 at 3:04:17 PM UTC+2, [email protected] wrote: > > >> I'm pretty sure that if you'll try the same without JaCoCo, then you'll >> observe exactly the same problem, which means that it is not caused by >> JaCoCo. >> > > Here do you mean i should try without instrumentation or with some other > instrumentation tools? >
Not "with some other tool", just without instrumentation by JaCoCo, which is a very good way to understand that problem is not caused by JaCoCo. And now you don't need to try anything, because you already know that problem was caused by bug in JMockit. On Monday, May 6, 2019 at 2:36:36 PM UTC+2, [email protected] wrote: > > > Thanks for the insights on this issue. I completely overlooked the > existing jmockit bug. > With the jmockit 1.46, the issue is gone. > -- 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/fb7646d7-b35e-4b14-8072-2cd719428868%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
