[ https://issues.apache.org/jira/browse/SUREFIRE-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742315#comment-17742315 ]
Michael Osipov edited comment on SUREFIRE-2187 at 7/12/23 8:25 AM: ------------------------------------------------------------------- It is extremely hard to cover all flavors of {{ps}}. was (Author: michael-o): It is extremely hard to cover all flavors of {{ps]]. > ps -p does not work in alpine or busy box by default > ---------------------------------------------------- > > Key: SUREFIRE-2187 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2187 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin > Affects Versions: 3.0.0 > Reporter: Martin Sillence > Priority: Minor > > Our builds were failing with the error: > System.exit() or native command error interrupted process checker. > java.lang.IllegalStateException: Cannot use PPID 687 process information. > Going to use NOOP events. > at > org.apache.maven.surefire.booter.PpidChecker.checkProcessInfo(PpidChecker.java:155) > checking the code it looks like you run ps -p: > [https://github.com/apache/maven-surefire/blob/47eb1974ef2fb77c621e5cb0c47ac10ab8f4753d/surefire-booter/src/main/java/org/apache/maven/surefire/booter/PpidChecker.java#L186C59-L186C71] > > installing procps in alipine seems to fix it > > I wonder if it is possible add something to check if ps supports the -p flag > as I imagine I'm not the only one to use alpine to build software? > Simply adding an error that the ps doesn't support -p would save significant > time -- This message was sent by Atlassian Jira (v8.20.10#820010)