[ https://issues.apache.org/jira/browse/SUREFIRE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429291#comment-16429291 ]
Michael Osipov commented on SUREFIRE-1512: ------------------------------------------ Tibor, there is no need to take it from the VM. I would rely on the OS, because this cannot be reasonably modified by the user. Just take the value, parse it timezone-sensitive, convert to Unix timestamp and you are done. > 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)