[
https://issues.apache.org/jira/browse/SUREFIRE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428397#comment-16428397
]
Michael Osipov commented on SUREFIRE-1512:
------------------------------------------
Here is the bug:
https://github.com/apache/maven-surefire/blob/b617a7522221d9be0de174215c817ccb609c30c7/surefire-booter/src/main/java/org/apache/maven/surefire/booter/ProcessInfo.java#L87-L100
The output has to be parsed and normalized to UTC for comparison. The asiest
would be cut the minute offset, covert to HH:mm and parse with
{{SimpleDateFormat}}. I hightly doubt that the Unix output is really comparable
too. I would parse that and convert to seconds.
> ProcessInfo for Windows is prone to timezone offset changes
> -----------------------------------------------------------
>
> Key: SUREFIRE-1512
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1512
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.21.0
> Reporter: Julian Reschke
> Priority: Major
>
> For some reason, on one of my machines, the current DST offset changes
> between calls. See
> <https://issues.apache.org/jira/browse/SUREFIRE-1444?focusedCommentId=16428263&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16428263>.
> This will cause surefire to think the forked VM terminated, as the string
> compare of time stamps detects a change.
> It would be good if the comparison code would actually parse the string value
> into a DST/TZ agnostic value for comparison.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)