[ https://issues.apache.org/jira/browse/OAK-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943220#comment-13943220 ]
Julian Reschke commented on OAK-1564: ------------------------------------- And the answer is over here: http://randomascii.wordpress.com/2013/07/08/windows-timer-resolution-megawatts-wasted/ - in my case, the timer resolution is 1ms when Chrome is running, and 10ms when it is not. > ClockTest on Windows fails > -------------------------- > > Key: OAK-1564 > URL: https://issues.apache.org/jira/browse/OAK-1564 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core > Environment: JAVA_HOME=C:\Program Files\Java\jdk1.7.0_51 > NUMBER_OF_PROCESSORS=2 > OS=Windows_NT > PROCESSOR_ARCHITECTURE=AMD64 > PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 46 Stepping 6, GenuineIntel > PROCESSOR_LEVEL=6 > PROCESSOR_REVISION=2e06 > Reporter: Michael Dürig > Assignee: Julian Reschke > Fix For: 0.20 > > Attachments: OAK-1564.diff > > > {{ClockTest.testClockDrift}} fails on Windows: > {noformat} > junit.framework.AssertionFailedError: unexpected drift: 26 (limit 20) > at junit.framework.Assert.fail(Assert.java:50) > at junit.framework.Assert.assertTrue(Assert.java:20) > at org.apache.jackrabbit.oak.stats.ClockTest.testClockDrift(ClockTest.java:72) > {noformat} -- This message was sent by Atlassian JIRA (v6.2#6252)