[
https://issues.apache.org/jira/browse/JCR-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941529#comment-13941529
]
Thomas Mueller commented on JCR-3743:
-------------------------------------
> whenever you expect currentTimeMillis to change, I'd simple busy-wait exactly
> for that
To avoid a 100% CPU loop, I would do:
{noformat}
while (System.currentTimeMillis() <= last) {
Thread.sleep(1);
}
{noformat}
> 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)
