On 04/23/2012 08:40 AM, Jacopo Cappellato wrote: > Adrian, > > the issue you are experiencing is interesting and I had a look at it; I was > only able to recreate the same failures by changing the timeouts in > UtilCacheTests.java at line 302 and 308; instead of: > > cache.setExpireTime(100); // line 302 > Thread.sleep(200); // line 308 > > I set: > > cache.setExpireTime(100); // line 302 > Thread.sleep(99); // line 308 > > and (of course) I got the error. > It is kind of weird that you are getting the error with the current settings > (100 and 200): is this consistent? I mean, are you able to recreate the issue > frequently? did you try to increase the time for sleep: > > Thread.sleep(300); // line 308
Ah, brilliant. Different platforms have different minimum time-slices. If my guess is correct, probably fixing this to run in *all* cases is really rather tricky. I'll definiately have a look at this, but it will take even longer to come up with a proper correct fix.
