[
https://issues.apache.org/jira/browse/SUREFIRE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1512:
-----------------------------------
Comment: was deleted
(was: [~reschke]
You know what is interesting that the times are from yesterday and you
immediately reported it even when we do not print these in dump file. The next
thing is interesting that the first time is greater but the next one is one
hour smaller. The minutes and seconds and microseconds are exactly the same.
This cannot be because next time sample should differ in one second because we
run the native commands every single second.)
> 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)
