[ 
https://issues.apache.org/jira/browse/SUREFIRE-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284260#comment-16284260
 ] 

Michael Osipov commented on SUREFIRE-1451:
------------------------------------------

[~tnn], I consider this to be a bug in NetBSD's {{ps(1)}} implementation. We 
have tested it with FreeBSD's one. The 
[manpage|http://netbsd.gw.com/cgi-bin/man-cgi?ps++NetBSD-current] says: "etime  
     elapsed time since the process was started, in the form 
\[\[dd-\]hh:\]mm:ss". You should report an issue with NetBSD and have it fixed 
in {{CURRENT}} and then MFCed to {{STABLE}}. Though, some leniency is fine 
here. The [FreeBSD 
code|https://github.com/freebsd/freebsd/blob/master/bin/ps/print.c#L581-L603] 
seems to be idiot-proof.

> Surefire Booter compatibility with NetBSD ps(1) output
> ------------------------------------------------------
>
>                 Key: SUREFIRE-1451
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1451
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: process forking
>    Affects Versions: 2.20.1
>         Environment: NetBSD
>            Reporter: Tobias Nygren
>            Assignee: Tibor Digana
>            Priority: Minor
>             Fix For: 2.21.0.Jigsaw
>
>
> On NetBSD The /bin/ps command reports time as 0:01 rather than 00:01 for 
> intervals shorter than 10 minutes.
> The pattern as used [here in SureFire 
> Booter|https://github.com/apache/maven-surefire/commit/c343cc412b986fd9da839696c709542d03679d68#diff-33826e7c2cc48fb008e88914fd841d10R71]
>  to parse ps(1) output does not take this into account.
> printf(3) logic for ps(1) can be found in the [ps 
> source|https://github.com/NetBSD/src/blob/9160f3e067c6f959b9ecb4296771d8a6ae9b3ee6/bin/ps/print.c#L832].
> The following patterns are possible and need to be accounted for:
> * m:ss
> * mm:ss
> * h:mm:ss
> * hh:mm:ss
> * d-hh:mm:ss
> * dd-hh:mm:ss



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to