Re: Restrict matrix tasks to specific nodes

Thanks for your help. I will monitor the build during the following days and verify that everything is alright. 2016-12-08 20:01 GMT+01:00 Gavin McDonald : > >> On 8 Dec. 2016, at 9:34 pm, Francesco Mari wrote: >> >> Hi, >> >> I recently

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

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #1321) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1321/ to view the results. Changes: [chetanm] OAK-4400 - Correlate index with the index

Re: Restrict matrix tasks to specific nodes

> On 8 Dec. 2016, at 9:34 pm, Francesco Mari wrote: > > Hi, > > I recently discovered that some of the tests run by the Apache > Jackrabbit Oak Matrix job [1] consistently fail when matrix tasks are > scheduled on one of the nodes labelled "beam". I documented the >

Oak 1.4.11 release plan

Hello team, I'm planning to cut Oak on Monday 12th Dec. If there are any objections please let me know. Otherwise I will re-schedule any non-resolved issue for the next iteration. Thanks Davide

Re: [VOTE] Release Apache Jackrabbit Oak 1.5.15

On 2016-12-08 13:04, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.5.15 Best regards, Julian

Re: [VOTE] Release Apache Jackrabbit Oak 1.5.15

[X] +1 Release this package as Apache Jackrabbit Oak 1.5.15 D.

Re: [VOTE] Release Apache Jackrabbit Oak 1.5.15

Hi, On 08/12/16 13:04, Davide Giannella wrote: > Please vote on releasing this package as Apache Jackrabbit Oak 1.5.15. > The vote is open for the next 72 hours and passes if a majority of at > least three +1 Jackrabbit PMC votes are cast. All checks OK. +1 Release this package as Apache

Re: [VOTE] Release Apache Jackrabbit Oak 1.5.15

[X] +1 Release this package as Apache Jackrabbit Oak 1.5.15 ALL CHECKS OK Thanks, Vikas

[VOTE] Release Apache Jackrabbit Oak 1.5.15

A candidate for the Jackrabbit Oak 1.5.15 release is available at: https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.5.15/ The release candidate is a zip archive of the sources in: https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.5.15/ The SHA1 checksum of

Restrict matrix tasks to specific nodes

Hi, I recently discovered that some of the tests run by the Apache Jackrabbit Oak Matrix job [1] consistently fail when matrix tasks are scheduled on one of the nodes labelled "beam". I documented the failures in this issue [2]. I would like to schedule the matrix tasks to run on specific nodes

Re: Frequent failures in standby test

In the meantime, I configured those tests not to run when they are scheduled under a "beam" node. I will send a separate mail to builds@ and put oak-dev@ in CC. 2016-12-08 11:23 GMT+01:00 Robert Munteanu : > Hi, > > On Thu, 2016-12-08 at 10:01 +0100, Francesco Mari wrote: >> I

Re: RIP Apache Jenkins!?

On Thu, 2016-12-08 at 10:46 +0100, Julian Reschke wrote: > On 2016-12-07 12:21, Michael Dürig wrote: > > > > In a F2F discussion we agreed to pay more attention to test > > failures on > > the Apache Jenkins instance and make an effort to turn it green: > > > > - tests that are constantly

Re: Frequent failures in standby test

Hi, On Thu, 2016-12-08 at 10:01 +0100, Francesco Mari wrote: > I analysed the latest builds to figure out what's going on with some > tests related to Cold Standby. It seems that the problem is > restricted > to some Jenkins nodes - see [1] for more details. Can we configure > the > Jenkins job

Re: RIP Apache Jenkins!?

>> Failed tests: externalAddOffline(org.apache. jackrabbit.oak.plugins.blob.datastore.BlobIdTrackerTest): expected:<1006> but was:<1001> Was added yesterdaytaking a look. Will Ignore it meantime. Thanks Amit On Thu, Dec 8, 2016 at 3:16 PM, Julian Reschke wrote: > On

Re: RIP Apache Jenkins!?

On 2016-12-07 12:21, Michael Dürig wrote: In a F2F discussion we agreed to pay more attention to test failures on the Apache Jenkins instance and make an effort to turn it green: - tests that are constantly failing and also fail on a local checkout should be marked @Ignored along with an issue

Re: Frequent failures in standby test

I analysed the latest builds to figure out what's going on with some tests related to Cold Standby. It seems that the problem is restricted to some Jenkins nodes - see [1] for more details. Can we configure the Jenkins job not to run on nodes labelled "beam"? [1]: