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

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

I am waiting for similar issues, for answer from SUREFIRE-1502 and I am
waiting for INFRA because I cannot rely on our Jenkins result since the
Windows machines have low free disk space.
In the GitHub pull requests are two simple fixes and improvements which are
also successful. Everything can be included in release.
I guess users in SUREFIRE-1502 are also waiting but I do not have Mac OS
and I am not able to reproduce Docker issue on Ubuntu however I tried that
using Docker CE.

On Thu, Apr 12, 2018 at 6:24 AM, Julian Reschke (JIRA) <j...@apache.org>



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

Reply via email to