before it does the exit it issues a loud log.error - so we'd have to have access to the log output..
besides resolving OAK-3250 when we know a test fails because of it, the easiest is to disable the leaseCheck as eg done in [0] but now test results of '381' are deleted so we can't find out anymore Cheers, Stefan -- [0] http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-core/src/test/java/or g/apache/jackrabbit/oak/plugins/document/VersionGarbageCollectorIT.java?r1= 1700741&r2=1700740&pathrev=1700741 On 07/09/15 10:25, "Michael Dürig" <[email protected]> wrote: > > >On 7.9.15 10:03 , Stefan Egli wrote: >> so perhaps it's a lease timeout case.. > >Any way to confirm this on Jenkins? E.g. could we place a println in >front of it? Or replace it with a throws? > >Michael
