[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454327#comment-16454327 ] Tibor Digana commented on SUREFIRE-1502: [~larry_west] Hi Larry, do you have a little time this week? Please run my small test project on you OS/X system. The project is in my comment https://issues.apache.org/jira/browse/SUREFIRE-1502?focusedCommentId=16434550=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16434550 We can start like this and then add more and more of what is contained in your project. > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446295#comment-16446295 ] Andreas Gudian commented on SUREFIRE-1502: -- I'm using macOS 10.13.4, Maven 3.5.3 and Surefire 2.21.0, JDK 8u144 and 8u171 without problems, including tests with a lot of stdout, with color and so on... In my own projects here and with the sample that Tibor provided above. So this is not a general macOS issue, I think. > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441416#comment-16441416 ] Tibor Digana commented on SUREFIRE-1502: [~Grim] Pls report the bug. It was good test, I think! > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:289) > at
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439918#comment-16439918 ] Tibor Digana commented on SUREFIRE-1502: [~Grim] Create a separate jira ticket. I executed your project but it is not related to this issue. Your problem has different root cause. I will explain everything in new ticket but not here. Thx. > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439315#comment-16439315 ] Peter Rader commented on SUREFIRE-1502: --- Similar [problem on Windows but with exit code 1|https://github.com/enexusde/source2runnablejar/tree/test-updated-surefire-version]. Maybe not a 100% duplicate . > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) >
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437375#comment-16437375 ] Paul Hammant commented on SUREFIRE-1502: Can we disambiguate what "OS/X 10" is please. These are the correct verion names/numbers for macOS (as it is known as today): |[OS X 10.8|https://simple.wikipedia.org/wiki/OS_X_Mountain_Lion]|Mountain Lion|February 16, 2012^[[17]|https://simple.wikipedia.org/wiki/MacOS#cite_note-PR-16-02-17]^|July 25, 2012^[[18]|https://simple.wikipedia.org/wiki/MacOS#cite_note-PR-25-07-18]^|10.8.5 (12F45) (October 3, 2013)| |[OS X 10.9|https://simple.wikipedia.org/wiki/OS_X_Mavericks]|Mavericks|June 10, 2013^[[19]|https://simple.wikipedia.org/wiki/MacOS#cite_note-PR-10-06-19]^|October 22, 2013|10.9.5 (13F1112) (September 18, 2014)| |[OS X 10.10|https://simple.wikipedia.org/wiki/OS_X_Yosemite]|Yosemite|June 2, 2014|October 16, 2014|10.10.5 (14F27) (August 13, 2015)| |[OS X 10.11|https://simple.wikipedia.org/wiki/OS_X_El_Capitan]|El Capitan|June 8, 2015|September 30, 2015|10.11.6 (15G1510) (May 15, 2017)| |[macOS 10.12|https://simple.wikipedia.org/w/index.php?title=MacOS_10.12=edit=1]|Sierra|June 13, 2016|September 20, 2016|10.12.6 (16G1212) (Jul 19, 2017)| |macOS 10.13|High Sierra|June 5, 2017|September 25, 2017|10.13.4 (17E150g) (March 29, 2018)| > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject >
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435256#comment-16435256 ] Tibor Digana commented on SUREFIRE-1502: [~khmarbaise] Hi Karl, do you have OS/X 10 can you make a simple test with Docker? In the comment from me above is a simple example what I did on Ubuntu x86_64 but the problem is that this issue is Mac related. > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435121#comment-16435121 ] Michael Osipov commented on SUREFIRE-1502: -- [~tibor17], no I do get access only once in a while. [~khmarbaise] could help. > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced >
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435013#comment-16435013 ] Tibor Digana commented on SUREFIRE-1502: [~michael-o] Do you have OS/X 10? Can you pls check it out on OS/X 10 and use the prototype with Docker in my previous comment? I think it must be a problem with calling native command because I tried on Ubuntu 17 and Docker CE 18.03 and it works. > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke >
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434550#comment-16434550 ] Tibor Digana commented on SUREFIRE-1502: [~larry_west] Larry, I created a docker project but it does not crash. It just runs 3 second. I tried several times. Can you please use my sources and tell me what's different with your use case on your system? {code:shell} sudo docker build --no-cache -t mymvn:1 -f ./Dockerfile . sudo docker run -it --rm mymvn:1 /bin/sh {code} Run the command {{mvn test}} in the shell console of docker. {{Dockerfile}} {code:shell} FROM maven:3.5.3-jdk-8-alpine COPY ./. / {code} {{src/test/java/MyTest.java}} {code:java} import org.junit.Test; public class MyTest { @Test public void test() throws InterruptedException { Thread.sleep(3000L); } } {code} {{pom.xml}} {code:xml} http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd;> 4.0.0 x x 1.0 junit junit 4.12 maven-surefire-plugin 2.21.0 {code} > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject >
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429713#comment-16429713 ] Tibor Digana commented on SUREFIRE-1502: [~larry_west] I have installed Docker and I am studying it but it would be faster if you just attache Dockerfile and POM in Jira and I will use it on Ubuntu 17. I will try to reproduce the issue but I guess I will have a problem to debug the JVM in docker. > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke >
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16421474#comment-16421474 ] Tibor Digana commented on SUREFIRE-1502: [~larry_west] [~carlos] [~raehalme] [~apottere] I've checked the code again and it can't be that you do not see dump files because every {{kill}} operation dumps a warning. There is very high suspicion the the pipes between Maven and Surefire Java processes are not able to share memory used to transfer standard output. You know what I mean? Native problem perhaps. The dump files (target/surefire-reports by default) are all about file system and pipes are mapped to file systems too. D you map host file system to Docker container's file system? > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415872#comment-16415872 ] Tibor Digana commented on SUREFIRE-1502: [~larry_west] We have to fix this. Please follow my previous comment. Thx. > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced >
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406025#comment-16406025 ] Tibor Digana commented on SUREFIRE-1502: [~larry_west] The branch hash is ok. Did you use also the snapshot version from ASF Maven Repository? I do not have Mac. I can only try out on x86-64 Ubuntu 16 or Fedora 24. Pls provide me with your project. You can attach it to Jira. If it is a commercial project and illegal to publish it, you can make a smaller one related only to this problem. And of course use the small project on your side again. Add there the {{Dockerfile}} and everything I need to reproduce this issue. Do you have the same problem also on Ubuntu? Thx > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > at
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405695#comment-16405695 ] Larry West commented on SUREFIRE-1502: -- [~tibor17] I cloned from the [https://github.com/apache/maven-surefire/tree/SUREFIRE-1422] branch ({{27f68718}}⋮) and stopped setting {{reuseForks=false}}, but get the same problem (twice) :( : {noformat} . . . [ERROR] Process Exit Code: 0 [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) . . . {noformat} I didn't try debugging it... let me know if there's more info or something else to try. > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403906#comment-16403906 ] Tibor Digana commented on SUREFIRE-1502: [~larry_west] I do not know why people write comments to SUREFIRE-1222. It was another issue and fixed and closed. Therefore I created another ticket https://issues.apache.org/jira/browse/SUREFIRE-1503 for version 3.0.0-M1 which contains a fix. > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke >
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403259#comment-16403259 ] Tibor Digana commented on SUREFIRE-1502: I think you are talking about the last discussion in Jira SUREFIRE-1422. The problem is that nobody who reported these issue has ever tested the fix which appears in the branch https://github.com/apache/maven-surefire/tree/SUREFIRE-1222 Would you do it? > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Fix For: 2.21.0 > > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > This occurs on roughly half the builds (with 2.21.0, at least). > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403179#comment-16403179 ] Larry West commented on SUREFIRE-1502: -- I just tried setting {{reuseForks=false}} and was able to build successfully seven times in a row. It might have been slower, but going back to earlier versions presents other problems for us. >From the {{mvn -X}} output on the *original, failing* build: {noformat} [INFO] --- maven-surefire-plugin:2.21.0:test (default-test) @ jsk-cc --- [DEBUG] Using mirror central-mirror (http://nexus-proxy/nexus/content/groups/public) for snapshots (http://snapshots.maven.codehaus.org/maven2). [DEBUG] Using mirror central-mirror (http://nexus-proxy/nexus/content/groups/public) for central (http://repo1.maven.org/maven2). [DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=313522, ConflictMarker.markTime=102477, ConflictMarker.nodeCount=114, ConflictIdSorter.graphTime=171914, ConflictIdSorter.topsortTime=41866, ConflictIdSorter.conflictIdCount=37, ConflictIdSorter.conflictIdCycleCount=0, ConflictResolver.totalTime=1118242, ConflictResolver.conflictItemCount=79, DefaultDependencyCollector.collectTime=50282293, DefaultDependencyCollector.transformTime=1773104} [DEBUG] org.apache.maven.plugins:maven-surefire-plugin:jar:2.21.0: [DEBUG]org.apache.maven.surefire:maven-surefire-common:jar:2.21.0:compile [DEBUG] org.apache.maven:maven-plugin-api:jar:2.2.1:compile [DEBUG] org.apache.maven.plugin-tools:maven-plugin-annotations:jar:3.5:compile [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.21.0:compile [DEBUG] org.apache.maven.surefire:surefire-logger-api:jar:2.21.0:compile [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.21.0:compile [DEBUG] org.apache.maven:maven-artifact:jar:2.2.1:compile [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.5.15:compile [DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.2.1:compile [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile [DEBUG] junit:junit:jar:4.12:compile [DEBUG]org.hamcrest:hamcrest-core:jar:1.3:compile [DEBUG] org.apache.maven:maven-project:jar:2.2.1:compile [DEBUG] org.apache.maven:maven-settings:jar:2.2.1:compile [DEBUG] org.apache.maven:maven-profile:jar:2.2.1:compile [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.2.1:compile [DEBUG] backport-util-concurrent:backport-util-concurrent:jar:3.1:compile [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.2.1:compile [DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.11:compile [DEBUG] org.apache.maven:maven-model:jar:2.2.1:compile [DEBUG] org.apache.maven:maven-core:jar:2.2.1:compile [DEBUG] org.apache.maven:maven-plugin-parameter-documenter:jar:2.2.1:compile [DEBUG] org.slf4j:slf4j-jdk14:jar:1.5.6:runtime [DEBUG] org.slf4j:slf4j-api:jar:1.5.6:runtime [DEBUG] org.slf4j:jcl-over-slf4j:jar:1.5.6:runtime [DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:3.0:compile [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.2.1:compile [DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.2.1:compile [DEBUG] org.apache.maven:maven-monitor:jar:2.2.1:compile [DEBUG] classworlds:classworlds:jar:1.1:compile [DEBUG] org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3:compile [DEBUG] org.sonatype.plexus:plexus-cipher:jar:1.4:compile [DEBUG] org.apache.maven:maven-toolchain:jar:2.2.1:compile [DEBUG] org.codehaus.plexus:plexus-java:jar:0.9.3:compile [DEBUG] org.ow2.asm:asm:jar:6.0_BETA:compile [DEBUG] com.thoughtworks.qdox:qdox:jar:2.0-M7:compile [DEBUG] Created new class realm plugin>org.apache.maven.plugins:maven-surefire-plugin:2.21.0 [DEBUG] Importing foreign packages into class realm plugin>org.apache.maven.plugins:maven-surefire-plugin:2.21.0 [DEBUG] Imported: < maven.api [DEBUG] Populating class realm plugin>org.apache.maven.plugins:maven-surefire-plugin:2.21.0 [DEBUG] Included: org.apache.maven.plugins:maven-surefire-plugin:jar:2.21.0 [DEBUG] Included: org.apache.maven.surefire:maven-surefire-common:jar:2.21.0 [DEBUG] Included: org.apache.maven.plugin-tools:maven-plugin-annotations:jar:3.5 [DEBUG] Included: org.apache.maven.surefire:surefire-api:jar:2.21.0 [DEBUG] Included: org.apache.maven.surefire:surefire-logger-api:jar:2.21.0 [DEBUG] Included: org.apache.maven.surefire:surefire-booter:jar:2.21.0 [DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:1.5.15 [DEBUG] Included: junit:junit:jar:4.12 [DEBUG] Included: org.hamcrest:hamcrest-core:jar:1.3 [DEBUG] Included: backport-util-concurrent:backport-util-concurrent:jar:3.1 [DEBUG] Included:
[jira] [Commented] (SUREFIRE-1502) Forking fails on OS/X
[ https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403148#comment-16403148 ] Larry West commented on SUREFIRE-1502: -- (I'm unable to edit the "Fix Version/s" field this is not fixed in 2.21.0) > Forking fails on OS/X > - > > Key: SUREFIRE-1502 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1502 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1, 2.21.0 > Environment: OS/X 10.13.3 > Java 1.8.0_162 >Reporter: Larry West >Assignee: Tibor Digana >Priority: Major > Fix For: 2.21.0 > > Attachments: surefire3972773662020453876tmp, > surefire_06790995305937656848tmp > > > This is very similar to SUREFIRE-1422, but is still present _intermittently_ > on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1. > The symptom is that all tests run fine (the reports are there), but as soon > as they do, there is an error: > {noformat} > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > ... > Process Exit Code: 0 > {noformat} > This of course fails the build. > Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3. > h5. Selected output from mvn -X > {noformat} > [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > {noformat} > ... then, after all the tests have run, successfully, it reports failure: > {noformat} > Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc && > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java > -jar > /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar > /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1 > surefire3972773662020453876tmp surefire_06790995305937656848tmp > Process Exit Code: 0 > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:671) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork > (ForkStarter.java:533) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:278) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run > (ForkStarter.java:244) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider > (AbstractSurefireMojo.java:1148) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked > (AbstractSurefireMojo.java:977) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute > (AbstractSurefireMojo.java:853) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:289) > at