[Oak origin/1.4] Apache Jackrabbit Oak matrix - Build # 1376 - Still Failing

2017-01-19 Thread Apache Jenkins Server
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #1376) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1376/ to view the results. Changes: [reschke] OAK-3683:

Re: [DocumentMK][LastRevRecovery] What should happen for indexing of commits that get recovered?

2017-01-19 Thread Vikas Saurabh
> That would be a bug. As part of the recovery for CN2, its _lastRev entry > will be updated to reflect the /tree/node2 change. Let's say previously it > was r7-0-2 and after the recovery is r9-0-2. The current > checkpoint for the async index update on CN1 does not yet see the updated > _lastRev.

Re: Collect data for test failure in issue itself

2017-01-19 Thread Michael Dürig
Good, point. +1 Michael On 19.1.17 10:32 , Chetan Mehrotra wrote: It would be helpful while renaming the Hudson created jira issue we also attach relevant unit-test.log from the module for which test failed and also record test failure message as comment This simplifies later analysis as CI

[ANNOUNCE] Apache Jackrabbit 2.10.5 released

2017-01-19 Thread Julian Reschke
The Apache Jackrabbit community is pleased to announce the release of Apache Jackrabbit 2.10.5. The release is available for download at: http://jackrabbit.apache.org/downloads.html See the full release notes below for details about this release: Release Notes -- Apache Jackrabbit --

[Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 1375 - Still Failing

2017-01-19 Thread Apache Jenkins Server
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #1375) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1375/ to view the results. Changes: [frm] OAK-5483 - Move TemporaryPort to the oak-commons

Collect data for test failure in issue itself

2017-01-19 Thread Chetan Mehrotra
It would be helpful while renaming the Hudson created jira issue we also attach relevant unit-test.log from the module for which test failed and also record test failure message as comment This simplifies later analysis as CI only retains reports for past few builds (not sure on number). For