[
https://issues.apache.org/jira/browse/SUREFIRE-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405994#comment-17405994
]
Michael Osipov edited comment on SUREFIRE-1941 at 8/27/21, 7:19 PM:
--------------------------------------------------------------------
This would be incomplete, it would also require to know how to parse the
output. The currect checks are tested and blessed. Don't you think so?
was (Author: michael-o):
This would be incomplete, it would also require to know how to parse the
output. The currect checked are tested and blessed. Don't you think so?
> Allow overriding PpidChecker OS command line in POM configuration
> -----------------------------------------------------------------
>
> Key: SUREFIRE-1941
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1941
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin, process forking
> Affects Versions: 2.22.2
> Reporter: Marc Batchelor
> Priority: Critical
>
> There are many Linux and Unix variants. The PpidChecker has received several
> fixes over time to handle various edge cases when checking to make sure that
> the process is still alive. When PpidChecker doesn't detect that the test is
> running because of some variant behavior as it relates to the output format
> of /bin/ps, the developer's only recourse is to disable forking which makes
> the test execution take longer.
> This improvement would allow a configuration setting to override the default
> command issued to the operating system to provide the process status in the
> form that PpidChecker can use.
> For example:
> {noformat}
> <plugin>
> ...
> <configuration>
> <ps-command>/other/bin/ps -o etime:1=,pid:1= -p %d</ps-command>
> </configuration>
> </plugin>{noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
