You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2018/05/06 11:35:00 UTC

[jira] [Updated] (SUREFIRE-1512) ProcessInfo for Windows is prone to timezone offset changes

     [ https://issues.apache.org/jira/browse/SUREFIRE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tibor Digana updated SUREFIRE-1512:
-----------------------------------
    Fix Version/s:     (was: 3.0.0-M1)
                   2.22.0

> 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
>            Assignee: Tibor Digana
>            Priority: Major
>             Fix For: 2.22.0
>
>
> 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)