The test failures in the issue seem to suggest that this may be relates to simple versionables. IIRC we recently added support for some broken JR2 constructs. Could they have been fixed in the last JR release? If that's the case it may no longer be possible to populate the source repository for the tests.
Just pure guesses, but I thought it might help. Regards Julian On Monday, February 15, 2016, Davide Giannella <dav...@apache.org> wrote: > On 12/02/2016 18:36, Manfred Baedke wrote: > > Hi, > > > > This is due to change 1721196 (associated with JCR-2633), which > > changes the persistent data model. Probably the test has just to be > > tweaked accordingly, I'll look into it during WE. > Thank you very much Manfred. > > I've filed https://issues.apache.org/jira/browse/OAK-4018 to keep track > and block 1.3.16. > > From here, once it's fixed in JR we have potentially 2 options: > > 1) unlock 1.3.16 by downgrading to JR 2.11.3 > 2) release JR 2.12.1, upgrade to Oak, release 1.3.16. Which will bring > the oak relase around 4-5 days late. > > I'm for two as it will give us more coverage around the inclusion of the > new stable JR release. > > Thoughts? > > Davide > > >
