[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987791#comment-16987791 ] Valerii Pekarskyi commented on SUREFIRE-1541: - [~tibordigana] thanks for your attention. You are right that there can be many causes to the mentioned error message. However as I commented my case was specifically caused by excessive logging that Windows console cannot handle fast enough My tests fail when I run them from Windows command line as "mvn verify". They however succeed when I try forkCount=0 or when I run "mvn verify >out.txt 2>&1", and I found that redirectTestOutputToFile worked in my specific case. That was definitely not an OOM, there was no hs_err files and Xmx setting did not help (and MaxPermSize has no effect for java 8). Upgrade from 2.22 to 3.0.0-M4 did not help either. Funny enough when I tried remote debugging of the test code issue disappeared maybe because output buffers were successfully dumped when breakpoint hit caused some execution delays. My intention was just to point to one more possible cause of the error message from the ticket description, and I hope it will help someone who found that OOM was not cause of their issue. Also maybe this message helps surefire developers with the investigation. I am not familiar with the plugin source, but suggest to check the fork creation code on Windows and how output buffers flush there. Here is the simple maven project with one test that prints some significant amount of text to stderr. On my environment it fails somewhere around 400's stack trace with junit 4.11 and around 350's with junit 5 (larger traces). Link to the repository: [https://github.com/Larry0ua/surefire-crash-report] > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Assignee: Tibor Digana >Priority: Major > Attachments: hs_err_pid3584.log > > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987756#comment-16987756 ] Tibor Digana commented on SUREFIRE-1541: We fixed several issues in the version {{3.0.0-M4}} (with Docker Alpine) which could cause these issues, and we disabled the process checker which can be enabled by the user (ping, native). All drawbacks are explained in the documentations. http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#enableProcessChecker See the notices in http://maven.apache.org/surefire/maven-surefire-plugin/examples/shutdown.html https://issues.apache.org/jira/browse/SUREFIRE-1689 https://issues.apache.org/jira/browse/SUREFIRE-1717 These are important fixex regarding Docker https://issues.apache.org/jira/browse/SUREFIRE-1702 https://issues.apache.org/jira/browse/SUREFIRE-1703 https://issues.apache.org/jira/browse/SUREFIRE-1704 https://issues.apache.org/jira/browse/SUREFIRE-1707 > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Assignee: Tibor Digana >Priority: Major > Attachments: hs_err_pid3584.log > > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987746#comment-16987746 ] Tibor Digana commented on SUREFIRE-1541: [~vpekar] Additionally, "excessive test output to Windows console" has nothing to do with "The forked VM terminated without properly saying goodbye" unless you are using JUnit47 Surefire provider (parallel=...). > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Assignee: Tibor Digana >Priority: Major > Attachments: hs_err_pid3584.log > > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987744#comment-16987744 ] Tibor Digana commented on SUREFIRE-1541: [~vpekar] You should not recommend this setting unless we understand the problem. Other people have other problems from you and they are always different. You have all the dump files from JVM and Surefire? Do you know if it is Out Of Memory (OOME)? If it is OOM then it is Javca settings problem with {{Xmx}} and {{MaxPermSize}}. > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Assignee: Tibor Digana >Priority: Major > Attachments: hs_err_pid3584.log > > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987732#comment-16987732 ] Valerii Pekarskyi commented on SUREFIRE-1541: - In my case issue was caused by excessive test output to Windows console, so redirecting mvn test stdout and stderr output to the file worked as a temporary solution. For others with the same issue I recommend surefire plugin configuration [key|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile] {code:java} true {code} > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Assignee: Tibor Digana >Priority: Major > Attachments: hs_err_pid3584.log > > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775865#comment-16775865 ] Tibor Digana commented on SUREFIRE-1541: The setting {{-Dmaven.failsafe.debug=false}} is default and not related to memory issues or setting. [~AthanasiosD] The users should see their attached {{"hs_err_pid3584.log"}} and that the tests run in forked JVM. Then the users should understand that a JVM without memory setting is JVM vendor specific (implicit Xmx is 1/4 of RAM). Then the tests have to be investigated for memory consumption and appropriate setting {{-Xmx1024m -XX:MaxPermSize=256m}} should be set or deeply investigate why your tests consume so much memory and do reference objects of finished test methods {{- broken Unit testing of tests isolation}}. See our documentation (parameter argLine): https://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Assignee: Tibor Digana >Priority: Major > Attachments: hs_err_pid3584.log > > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773999#comment-16773999 ] Athanasios Doulgeris commented on SUREFIRE-1541: The exact same issue as [~rivanov]'s screenshot persists for Windows 10, OpenJDK 11.0.2, Maven 3.6.0 and Maven 3.5.4, Surefire 2.20 up to 3.0.0-M3 using the following command works though: {code:java} mvn clean install > my_log.log {code} Is there any update on the issue? > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Assignee: Tibor Digana >Priority: Major > Attachments: hs_err_pid3584.log > > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686107#comment-16686107 ] Tibor Digana commented on SUREFIRE-1541: [~rivanov] As I said, this is another reason of the fault. You have got an Out of Memory Error. {{The system is out of physical RAM or swap space}}. > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Assignee: Tibor Digana >Priority: Major > Attachments: hs_err_pid3584.log > > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686059#comment-16686059 ] Radoslav Ivanov commented on SUREFIRE-1541: --- Should we change the memory settings - note the attached.[^hs_err_pid3584.log] > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Assignee: Tibor Digana >Priority: Major > Attachments: hs_err_pid3584.log > > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685973#comment-16685973 ] Tibor Digana commented on SUREFIRE-1541: [~rivanov] You use Docker or Vagrant or normal host? If it is normal host then it is not still reproducible but it is another issue. Do you see the first line [ERROR], can you find the dump files and attach them? You used another java version as well? > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Assignee: Tibor Digana >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685852#comment-16685852 ] Radoslav Ivanov commented on SUREFIRE-1541: --- This issue is still reproducible on Windows with OpenJDK 11, Maven 3.6.0 and SURFIRE plugin 3.0.0-M1 {code:java} [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream. [ERROR] The forked VM terminated without properly saying goodbye. VM crash or System.exit called? [ERROR] Command was cmd.exe /X /C "D:\jdk\openjdk-11\bin\java -Dformcenter.version=18.11.0 -jar C:\Users\dev\AppData\Local\Temp\surefire15361055596163701059\surefirebooter7359148605052433678.jar C:\Users\dev\AppData\Local\Temp\surefire15361055596163701059 2018-11-13T15-01-05_359-jvmRun2 surefire9627993971155929482tmp surefire_74224518744146218853tmp" [ERROR] Error occurred in starting fork, check output in log [ERROR] Process Exit Code: 1 [ERROR] Crashed tests: [ERROR] com.avoka.tm.workspace.impl.CategoryApiServiceImplTestCase [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called? [ERROR] Command was cmd.exe /X /C "D:\jdk\openjdk-11\bin\java -Dformcenter.version=18.11.0 -jar C:\Users\dev\AppData\Local\Temp\surefire15361055596163701059\surefirebooter7359148605052433678.jar C:\Users\dev\AppData\Local\Temp\surefire15361055596163701059 2018-11-13T15-01-05_359-jvmRun2 surefire9627993971155929482tmp surefire_74224518744146218853tmp" [ERROR] Error occurred in starting fork, check output in log [ERROR] Process Exit Code: 1 [ERROR] Crashed tests: {code} Any suggestions on how to solve it would be much appreciated. > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Assignee: Tibor Digana >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681677#comment-16681677 ] Tibor Digana commented on SUREFIRE-1541: [~patsevanton] No, it's not a beta. It's release candidate. We used Java 1.7 and Maven API 3.0 and we fixed {{SUREFIRE-1588}} which is fix for your problem. The API 3.0 and java 1.7 is a MUST for our plugin version 3.0.0 but since we are expecting more dramatic changes, that we cannot do after the release 3.0.0, we have release the mandatory M1 first of all and then we will continue with more release candidates which break some backwards compatibility (but not everything of course - only those API which fix critical and blocker issues - see Jira). > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681665#comment-16681665 ] Anton commented on SUREFIRE-1541: - Yes. maven-surefire-plugin 3.0.0-M1 with maven:3.6.0-jdk-8 fixed issue. Thx! maven-surefire-plugin 3.0.0-M1 - is beta? when new stable release? > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681586#comment-16681586 ] Tibor Digana commented on SUREFIRE-1541: [~patsevanton] Use the latest version {{3.0.0-M1}} of the plugin together with {{maven:3.5.4-jdk-8}} and let me know the result. Thx > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681572#comment-16681572 ] Tibor Digana commented on SUREFIRE-1541: [~bchupika] Do not use this workaround. I think you have totally different problem - SUREFIRE1588. Use the latest version {{3.0.0-M1}}. > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681552#comment-16681552 ] Bohdan Chupika commented on SUREFIRE-1541: -- Hi, [~patsevanton] I had the same error. Solved this by adding *false* property: {code:java} org.apache.maven.plugins maven-surefire-plugin ${mavenSurefirePluginVersion} org.apache.maven.surefire surefire-junit47 2.20.1 false false **/*.class com.my.package.IntegrationTest {code} > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678047#comment-16678047 ] Anton commented on SUREFIRE-1541: - mvn test [https://gitlab.com/anton_patsev/java-junit-sample/-/jobs/117458203/artifacts/browse/target/surefire-reports/] mvn verify [https://gitlab.com/anton_patsev/java-junit-sample/-/jobs/117458204/artifacts/browse/target/surefire-reports/] > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677972#comment-16677972 ] Tibor Digana commented on SUREFIRE-1541: [~patsevanton] [~sawo] ??Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.?? It would speed up the investigating the problem if you attached the dump file (see {{target/surefire-reports}}) directly from Docker run. > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677944#comment-16677944 ] Sander Wozniak commented on SUREFIRE-1541: -- We have observed the same issue in our project (both inside and outside of Docker). It seems to also affect older releases of the plugin (2.19.1). Maven 3.6.0 and 3.5.4 did not work, downgrading to 3.5.3 solved the issue. > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674551#comment-16674551 ] Tibor Digana commented on SUREFIRE-1541: [~patsevanton] Not sure yet if you can help right now. We will ask you for a help after we have reproduced the issue. > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674538#comment-16674538 ] Anton commented on SUREFIRE-1541: - I am not debugging Surefire forked process via Docker. I am try run test maven-failsafe-plugin in gitlab ci (Docker) How i can help for fix this issue? (i am DevOps) > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674469#comment-16674469 ] Tibor Digana commented on SUREFIRE-1541: [~abotos] I think {{getDebugForkedProcess()}} has nothing to do with the stacktrace. It's strange to me that you are debugging Surefire forked process via Docker. The PING events are not checked while debugging. So. This should not kill the subprocess. We should check it out without Docker. > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674063#comment-16674063 ] Anton commented on SUREFIRE-1541: - maven:3.6.0-jdk-8 surefire 2.22.1 - FAILED https://gitlab.com/anton_patsev/java-junit-sample/-/jobs/116087079 > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672945#comment-16672945 ] Anton commented on SUREFIRE-1541: - h3. maven:3.5.4-jdk-8 surefire 2.22.1 - FAILED https://gitlab.com/anton_patsev/java-junit-sample/-/jobs/115721004 h3. maven:3.5.3-jdk-8 surefire 2.22.1 - SUCCESS https://gitlab.com/anton_patsev/java-junit-sample/-/jobs/115721102 > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672884#comment-16672884 ] Anton commented on SUREFIRE-1541: - If i use maven:3.3.9-jdk8 surefire 2.22.1 - i dont get error https://gitlab.com/anton_patsev/java-junit-sample/-/jobs/115700267 > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672854#comment-16672854 ] Anton commented on SUREFIRE-1541: - Hello! I get same error: ??8325 [ERROR] Error occurred in starting fork, check output in log?? ??8331 [ERROR] Process Exit Code: 1?? ??8331 [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called??? Full log [https://gitlab.com/anton_patsev/java-junit-sample/-/jobs/115679279] Repository [https://gitlab.com/anton_patsev/java-junit-sample] > SurefireBooterForkException: The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > -- > > Key: SUREFIRE-1541 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1541 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 >Reporter: Anghel Botos >Priority: Major > > Attempting to run integration tests using maven-failsafe-plugin with > {{-Dmaven.failsafe.debug=false}} yields the following stacktrace: > > {noformat} > [ERROR] ExecutionException The forked VM terminated without properly saying > goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" false -jar > C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar > C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 > 2018-07-24T11-18-12_704-jvmRun1 surefire7184511894589995478tmp > surefire_411836142070426630764tmp" > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) > {noformat} > > The issue is the "free-floating" {{false}} that appears in the command line > used to start a new JVM. I've traced down the issue to > {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}} > where the following code can be found: > {code:java} > String debugForkedProcess = getDebugForkedProcess(); > if ( "true".equals( debugForkedProcess ) ) > { > return "-Xdebug -Xnoagent -Djava.compiler=NONE" > + " > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"; > } > return debugForkedProcess; > {code} > ...which is quite..."unexpected" to see that one can pass in a value of > {{true}}, but not a value of {{false}}. > Please fix with a proper parsing of true/false values for the > {{maven.failsafe.debug}} property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)