On Friday, December 28, 2018 at 7:02:18 AM UTC-12, Evgeny Mandrikov wrote: > On Friday, December 28, 2018 at 8:39:35 AM UTC+1, [email protected] wrote: > > I have observed one new thing while execution of "maven-surefire-plugin" i.e. > when I keep forkCount as 0(zero) in my surefire plugin it executes the tests > but gives message as "Skipping JaCoCo execution due to missing execution data > file". > > > > Have you ever tried to understand what forkCount zero means? > > It means that maven-surefire-plugin won't start new JVM for execution of > tests and will run tests inside JVM that executes Maven. > Hence there is no way to set JVM arguments such as "-javaagent". > This is also described in JaCoCo documentation at page > https://www.jacoco.org/jacoco/trunk/doc/maven.html : > > > > When using the maven-surefire-plugin you must not use a forkCount of 0 or set > the forkMode to never as this would prevent the execution of the tests with > the javaagent set and no coverage would be recorded. > > > On Friday, December 28, 2018 at 8:39:35 AM UTC+1, [email protected] wrote: > > However, when I give the forkCount as 1 then it gives me the below error, > > [ERROR] The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:671) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:278) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:244) > [ERROR] at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1194) > [ERROR] at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1022) > [ERROR] at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:868) > [ERROR] at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137) > > > On Friday, December 28, 2018 at 12:55:36 PM UTC+1, [email protected] > wrote:However, I didn't understand one thing if the same configuration is > working on my newly created sample example why the same configuration is not > working in my project module? > > > As was said to you many times - the reason might be not in configuration, but > for example in your tests! And that's why guessing based on just pom.xml is > useless! > > > > There are plenty of reasons for the above message, starting from insufficient > memory for JVM, including bugs in tests and bugs in JDK, and etc - > http://lmgtfy.com/?q=%22The+forked+VM+terminated+without+properly+saying+goodbye.%22 > > So could you please finally make an effort to properly investigate this > before posting your next observation here?
@Evgeny Mandrikov I already read about it at jacoco documentation page and that's the reason I have kept it as 1 in my configuration instead of keeping it as zero. -- 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/3678bde6-58b0-4c15-86a7-7b57bf518fcf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
