No session/execution data - and no error

[yaniv....@gmail.com]

Hi,
Running jacoco using the jacoco-maven-plugin, v0.8.1. All was working well until at a certain point, for one of the sub-modules, I started getting no execution data (and no session). Coverage for the rest of the sub-modules continued working fine. With a lot of trial and error (including tests little by little) I was able to find a single unit test (out of 700) that causes the jacoco problem - skipping this test makes the problem go away, meaning jacoco works fine and produces a session with coverage info. The thing is - I have no idea what the problem is, since there is no error reported - I'm just getting an empty jacoco.exec file (size 0B). Getting maven to print all the debug information does not give info related to the problem either. Can anyone recommend how to investigate this?

[Marc Hoffmann]

Hi,

there is a good chance that you stepped in a JDK Bug which is described here:

https://github.com/jacoco/eclemma/issues/64

https://bugs.openjdk.java.net/browse/JDK-8154017

Can you please check whether the specific test puts the main thread into interrupted state?

Thanks,

-marc

On 25. May 2018, at 22:38, yaniv....@gmail.com wrote:

Hi,
Running jacoco using the jacoco-maven-plugin, v0.8.1. All was working well until at a certain point, for one of the sub-modules, I started getting no execution data (and no session). Coverage for the rest of the sub-modules continued working fine. With a lot of trial and error (including tests little by little) I was able to find a single unit test (out of 700) that causes the jacoco problem - skipping this test makes the problem go away, meaning jacoco works fine and produces a session with coverage info. The thing is - I have no idea what the problem is, since there is no error reported - I'm just getting an empty jacoco.exec file (size 0B). Getting maven to print all the debug information does not give info related to the problem either. Can anyone recommend how to investigate this?

--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/de675e0a-f7f0-4a1d-ba66-2eeaf59033bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[yaniv....@gmail.com]

Thanks Marc,
I don't believe this is the case - it were, I'd see the "Error while dumping coverage data (code 5013)." error message. I don't see ANY error message, this is basically the biggest issue here.

[Marc Hoffmann]

Sorry for the confusion: This error message only applies for the JaCoCo Eclipse plugin. For the Maven plugin the outcome in this situation is an empty exec file.

Regards,
-marc

> On 26. May 2018, at 13:54, yaniv....@gmail.com wrote:
>
> Thanks Marc,
> I don't believe this is the case - it were, I'd see the "Error while dumping coverage data (code 5013)." error message. I don't see ANY error message, this is basically the biggest issue here.
>

> --
> 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+un...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/80b8ddaf-1e74-42cb-bf99-1052d44e844d%40googlegroups.com.

[yaniv....@gmail.com]

I ran coverage in eclipse and indeed got error 5013. Thanks Marc!

[Marc Hoffmann]

Ok, then most likely this is the before-mentioned issue.

You have two options:

1) Rework your test to not leave the main thread in interrupted state (recommended, as this may also cause other issues)
2) Upgrade to a recent JDK which fixes the issue

Regards,
-marc

> On 27. May 2018, at 10:48, yaniv....@gmail.com wrote:
>
> I ran coverage in eclipse and indeed got error 5013. Thanks Marc!
>

> --
> 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+un...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/161a6685-13bf-44ff-8d7c-8c99b9e076f8%40googlegroups.com.

[yaniv....@gmail.com]

This is a test that uses Jersey's Test Framework (a test extending JerseyTest) , so I suspect it's jersey that interrupts the main thread in its shutdown code. It's definitely not directly my test or production code.
Thanks for the suggestions.

[Marc Hoffmann]

Then you need to update to an JDK which fixes the issue. Please see OpenJDK ticket for fix versions.

Cheers,
-marc

> On 27. May 2018, at 14:54, yaniv....@gmail.com wrote:
>
> This is a test that uses Jersey's Test Framework (a test extending JerseyTest) , so I suspect it's jersey that interrupts the main thread in its shutdown code. It's definitely not directly my test or production code.
> Thanks for the suggestions.
>

> --
> 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+un...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/dfe5d30a-1097-4e3d-90c7-3ffb025c4d74%40googlegroups.com.