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

Tibor Digana commented on SUREFIRE-1512:
----------------------------------------

[~reschke]
What was the time zone with the times you reported in Jira? The DST happened 
after 2pm?
I want to simulate the same in unit tests.
[1]: 20180406142327.741074+120, 20180406132327.741074+060

[~michael-o]
I will take the time zone from Maven process. I think it is necessary. We 
cannot take it from forked surefire VM because the user may change the time 
zone in {{argLine}} parameter. WDYT?

> 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
>
> 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