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

Bertrand Delacretaz commented on JCR-3743:
------------------------------------------

[~julian.resc...@gmx.de] I'm curious, why 20ms specifically? 

I'm aware of the granularity problem, so in general terms the only sure things 
is that System.currentTimeMillis() increases from time to time...why 20ms?

> failing test if aws extensions
> ------------------------------
>
>                 Key: JCR-3743
>                 URL: https://issues.apache.org/jira/browse/JCR-3743
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>            Reporter: Julian Reschke
>            Assignee: Dominique Pfister
>            Priority: Minor
>
> On Win7/64bit/corei7:
> Failed tests:
>   testDeleteAllOlderThan(org.apache.jackrabbit.aws.ext.ds.TestInMemDs)
>   testDeleteAllOlderThan(org.apache.jackrabbit.aws.ext.ds.TestInMemDsCacheOff)
> Likely because of incorrect assumptions about System.currentTimeMillis()



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to