Ok, that was a silly comment, you already added the OS info to the issue :)
Julian, could we go on with this release and focus on fixing JCR-3743 for the next one? best, alex On Mon, Mar 17, 2014 at 1:33 PM, Alex Parvulescu <[email protected]>wrote: > could this be platform related? > > it doesn't fail on my end > > > > On Mon, Mar 17, 2014 at 12:54 PM, Julian Reschke <[email protected]>wrote: > >> On 2014-03-14 16:38, Alex Parvulescu wrote: >> >>> Hi, >>> >>> A candidate for the Jackrabbit 2.7.5 release is available at: >>> >>> https://dist.apache.org/repos/dist/dev/jackrabbit/2.7.5/ >>> >>> The release candidate is a zip archive of the sources in: >>> >>> https://svn.apache.org/repos/asf/jackrabbit/tags/2.7.5/ >>> >>> The SHA1 checksum of the archive is >>> 63c4ac873c84c4e77f235ba007f7b354cf926e49. >>> >>> A staged Maven repository is available for review at: >>> >>> https://repository.apache.org/content/repositories/ >>> orgapachejackrabbit-1006/ >>> >>> The command for running automated checks against this release candidate >>> is: >>> >>> $ sh check-release.sh 2.7.5 63c4ac873c84c4e77f235ba007f7b3 >>> 54cf926e49 >>> >>> Please vote on releasing this package as Apache Jackrabbit 2.7.5. >>> The vote is open for the next 72 hours and passes if a majority of at >>> least three +1 Jackrabbit PMC votes are cast. >>> >>> [ ] +1 Release this package as Apache Jackrabbit 2.7.5 >>> [ ] -1 Do not release this package because... >>> >>> >>> My vote is +1 >>> ... >>> >> >> The build fails over here: >> >> Running org.apache.jackrabbit.core.data.TestInMemDs >> Tests run: 9, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 8.21 sec >> <<< FAILURE! >> >> Results : >> >> Failed tests: >> >> testUpdateLastModifiedOnAccess(org.apache.jackrabbit.core. >> data.TestInMemDsCacheOff) >> >> testDeleteAllOlderThan(org.apache.jackrabbit.core.data. >> TestInMemDsCacheOff) >> >> testUpdateLastModifiedOnAccess(org.apache.jackrabbit.core. >> data.TestInMemDs) >> testDeleteAllOlderThan(org.apache.jackrabbit.core.data.TestInMemDs) >> >> >> (this is likely <https://issues.apache.org/jira/browse/JCR-3743>) >> >> Best regards, Julian >> > >
