I double-checked my commit, but there really does not seem there is anything in there that might have triggered the failure of ConcurrentImportTest. I think it must be some change in your local environment.
-- Unico On Wed, Jan 30, 2013 at 1:31 PM, Jukka Zitting <[email protected]> wrote: > Hi, > > On Wed, Jan 30, 2013 at 2:06 PM, Unico Hommes <[email protected]> wrote: >> The testfailure on the quoted url is not related to the unit test >> mentioned in the issue you created. In fact ConcurrentImportTest runs >> fine on my machine. The failing test in that report is >> org.apache.jackrabbit.core.persistence.AutoFixCorruptNode.testAutoFixWithConsistencyCheck. > > Oh, indeed! My mistake. > > However, the ConcurrentImportTest does currently fail in my > environment, so I wonder if this is relate to JCR-3277 or something > different, perhaps triggered by some change in my enviroment. > > BR, > > Jukka Zitting
