"Otis Gospodnetic" <[EMAIL PROTECTED]> wrote: > Just saw this test fail: > > [junit] Testcase: > > testExpirationTimeDeletionPolicy(org.apache.lucene.index.TestDeletionPolicy): > FAILED > [junit] commit point was older than 2.0 seconds but did not get > deleted > [junit] junit.framework.AssertionFailedError: commit point was older > than 2.0 seconds but did not get deleted > [junit] at > > org.apache.lucene.index.TestDeletionPolicy.testExpirationTimeDeletionPolicy(TestDeletionPolicy.java:229) > [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > [junit] at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [junit] at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > > Is my G4 Powerbook too slow? ;) It does take 15 minutes to run the > complete test suite. > > Subsequent runs of just this tests were all successful, but it did fail > once, as shown above.
Hmmm. That test verifies that a time based deletion policy (remove a commit point only if it's older than X seconds) is working properly. I added it (recently) for LUCENE-710. OK I think I see where this test is wrongly sensitive to the speed of the machine it's running on and would then cause a false positive failure. I will commit a fix. Still, Otis, I think you should upgrade to a MacBook Pro :) Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
