Slow tests

Hi all, I opened OAK-3858 to discuss about some slow running tests. I would like to raise awareness to the whole team, since I don't have enough background in every subsystem to evaluate if a test is slow because of a potential bug, if it should be moved to the integration test phase, or if it

Re: JIRA issue not showing associated commits

Hmm, I used this a lot too, so it would be *very* nice to get it back. should we take this up with infra? alex On Mon, Jan 4, 2016 at 5:26 AM, Chetan Mehrotra wrote: > Hi Team, > > Earlier the JIRA for Oak used to show commits related to the issues via > fisheye

Re: JIRA issue not showing associated commits

Hi, On Mon, Jan 4, 2016 at 5:26 AM, Chetan Mehrotra wrote: >... Any idea on how to get that integration back? Probably when we moved to > Epic based model it got lost... I suspect (but I'm not sure) that feature was turned off by ASF infrastructure for performance

[Oak origin/1.0] Apache Jackrabbit Oak matrix - Build # 665 - Failure

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #665) Status: Failure Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/665/ to view the results. Changes: [reschke] OAK-3852: RDBDocumentStore: batched append logic may loose

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

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #666) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/666/ to view the results. Changes: [reschke] OAK-3852: RDBDocumentStore: batched append logic may

Re: Slow tests

On 2016-01-11 11:56, Francesco Mari wrote: Hi all, I opened OAK-3858 to discuss about some slow running tests. I would like to raise awareness to the whole team, since I don't have enough background in every subsystem to evaluate if a test is slow because of a potential bug, if it should be

Re: Running tests without the baseline check?

I don't have a better solution to it. The baseline check is not a test, and it should not be deactivated when skipTests is true. As pointed out by Robert, the baseline goal already has its own property to skip itself (baseline.skip), so I see no need to use skipTests. Unless someone disagree, I

Running tests without the baseline check?

Hi, Working on a branch makes it quite inconvenient to run baseline checks so until I rebase. I have tried running the build with -Dbaseline.skip=true but that does nothing. The only 'fix' is to patch oak-parent/pom.xml: diff --git a/oak-parent/pom.xml b/oak-parent/pom.xml index