[
https://issues.apache.org/jira/browse/SUREFIRE-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16402091#comment-16402091
]
ASF GitHub Bot commented on SUREFIRE-1479:
------------------------------------------
GitHub user jbliznak opened a pull request:
https://github.com/apache/maven-surefire/pull/179
[SUREFIRE-1479] Force UNIX Standard mode for ps command on HP-UX OS
[SUREFIRE-1479](https://issues.apache.org/jira/browse/SUREFIRE-1479)
Workaround different set of arguments of ps command on HP-UX by switching
it into UNIX Standard mode.
http://www.polarhome.com/service/man/?qf=ps&tf=2&of=HP-UX&sf=1
http://www.polarhome.com/service/man/?qf=standards&tf=2&of=HP-UX&sf=5
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbliznak/maven-surefire SUREFIRE-1479
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-surefire/pull/179.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #179
----
commit 9e8c51ecc3029e7b3e0aa0b6d7721ad0a37426e4
Author: Jan Bliznak <jbliznak@...>
Date: 2018-03-16T15:53:42Z
[SUREFIRE-1479] Force UNIX Standard mode for ps command on HP-UX OS
----
> SurefireBooterForkException: The forked VM terminated without properly saying
> goodbye since 2.20.1
> --------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1479
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1479
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.20.1
> Reporter: Ondrej Lukas
> Priority: Major
>
> After upgrade to maven surefire plugin to version 2.20.1 (from version 2.20)
> our testsuite start to fail on HP-UX with:
>
>
> {code:java}
> Process Exit Code: 1 at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:496)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:443)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:295)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:246)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> 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:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107) at
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:955) 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
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?{code}
>
>
> This exception is thrown and no test cases are run.
>
> I believe that this issue in not dependent on HP-UX since I found the same
> issue for windows [1], but it seems it has not been reported yet.
>
> Since the only change between correct test execution and thrown exception is
> just change of surefire version I believe this is regression.
>
> [1]
> [https://stackoverflow.com/questions/48631856/maven-surefire-forked-vm-terminated-issue-in-windows]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
