[jira] [Commented] (SUREFIRE-1512) ProcessInfo for Windows is prone to timezone offset changes

["Jan Mosig (JIRA)" <ji...@apache.org>]

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

Jan Mosig commented on SUREFIRE-1512:
-------------------------------------

FYI I did encounter this bug while using surefire 2.19.1 with failsafe 2.20.1. In this case a workaround for this bug is to disable JVM forking in failsafe:
{code:java}
<build>
<plugins>
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-failsafe-plugin</artifactId>
    <configuration>
        <forkMode>none</forkMode>
    </configuration>
</plugin>
</plugins>
</build>{code}
 

> 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: 2.22.0
>
>
> 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)