On 15/07/14 09:57, "Marcel Reutegger" <[email protected]> wrote: >not caused by my commit but rather the clock issue again: > >testClockDrift(org.apache.jackrabbit.oak.stats.ClockTest) Time elapsed: >0.223 sec <<< FAILURE! >junit.framework.AssertionFailedError: Clock.Fast unexpected drift: -38ms >(estimated limit was 5ms, measured granularity was 1.0ms)
hmm, this means the clock is behind 38 milliseconds, right? the fast clock value is updated with a scheduled task every millisecond. isn't it quite likely that the clock falls behind for a short while when e.g. the garbage collector kicks in? regards marcel
