[
https://issues.apache.org/jira/browse/SUREFIRE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394433#comment-16394433
]
ASF GitHub Bot commented on SUREFIRE-1422:
------------------------------------------
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/178
SUREFIRE-1422
Related to JIRA
[SUREFIRE-1422](https://issues.apache.org/jira/browse/SUREFIRE-1422).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/maven-surefire SUREFIRE-1422
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-surefire/pull/178.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 #178
----
commit 27f68718b7cd7d73ae7488fb8b971c3d74becdef
Author: Tibor17 <tibordigana@...>
Date: 2018-03-10T16:10:35Z
SUREFIRE-1422
----
> Forking fails on Linux if /bin/ps isn't available
> -------------------------------------------------
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
> Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
> Reporter: Emmanuel Bourg
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 2.21.0
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at
> least check its existence and display an explicit message stating that it
> must be installed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
