Jörg Schaible wrote: > Hi folks, > > I have written a generator for commons-id, that is based in the end on the > system clock. Unfortunately I have sporadic failures in Gump that I cannot > explain. I developed this on a Windows box, but had now a chance for a > test with Linux. Suddenly I have also sporadic failing tests. First I > thought my algorithm is flawed, but then I wrote this little unit test: > > > public void testSystemTimeIsIncreasing() { > long last = System.currentTimeMillis(); > for (int i = 0; i < 50000; i++) { > long now = System.currentTimeMillis(); > assertTrue("Iteration " + i, now >= last); > last = now; > } > } > > > Believe it or not, this test will quite always fail within the first 10000 > iterations on my Linux box. So how does this test behave on your boxes? > Please also note OS and JDK ...
OK, I can analyse the situation. My current box was not totally synchronized and I had a daemon running, that adjusted the time smoothly. After compete synchronization the tests passes. Nevertheless, this does not solve the Gump problem, since I know, that they have often problems with the system time (we had last week one VM where 1 second exactly took 2 real ones). So what can we do? - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]