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/04/11 20:55:00 UTC
[jira] [Closed] (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 closed SUREFIRE-1512.
----------------------------------
Resolution: Fixed
https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=c546235573817a32155b0413029b4d0a8b1f80d6
> 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)