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

Julian Reschke commented on SUREFIRE-1512:
------------------------------------------

[~tibor17] - right now it does. I have confirmed by having it fail with 2.21.0, 
having it pass with the snapshot version, and having it fail again with 2.21.0.

My workaround is to run with the machine running with UTC timezone (which does 
not have DST).

> 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: 3.0.0-M1
>
>
> 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)

Reply via email to