Re: [Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 381 - Failure

2015-09-07 Thread Michael Dürig 



On 7.9.15 10:03 , Stefan Egli wrote:

so perhaps it's a lease timeout case..


Any way to confirm this on Jenkins? E.g. could we place a println in 
front of it? Or replace it with a throws?


Michael

Oak releases and profiles

2015-09-07 Thread Marcel Reutegger 
Hi,

most of us probably use the automated release checker script
we have for Jackrabbit and Oak releases. I recently noticed
the check script returns rather quickly for Oak releases. It
turns out this is due to profiles and configuration we have
in Oak.

The script runs 'mvn verify -Ppedantic'

For Oak, this means tests are skipped, because we wanted to
use this profile on Jenkins to run the RAT plugin only.

I would like to revert this change and run tests again
with the pedantic profile. This ensures we check the release
as documented in the README.md where users are instructed
to run 'mvn clean install' or 'mvn clean install -PintegrationTesting'.

Regards
 Marcel

Re: [Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 381 - Failure

2015-09-07 Thread Stefan Egli 
before it does the exit it issues a loud log.error - so we'd have to have
access to the log output..

besides resolving OAK-3250 when we know a test fails because of it, the
easiest is to disable the leaseCheck as eg done in [0]

but now test results of '381' are deleted so we can't find out anymore

Cheers,
Stefan
--
[0] 
http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-core/src/test/java/or
g/apache/jackrabbit/oak/plugins/document/VersionGarbageCollectorIT.java?r1=
1700741=1700740=1700741

On 07/09/15 10:25, "Michael Dürig"  wrote:

>
>
>On 7.9.15 10:03 , Stefan Egli wrote:
>> so perhaps it's a lease timeout case..
>
>Any way to confirm this on Jenkins? E.g. could we place a println in
>front of it? Or replace it with a throws?
>
>Michael

Re: [Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 381 - Failure

2015-09-07 Thread Stefan Egli 
'... System.exit called ...'

what we currently have until OAK-3250 is fixed is a System.exit when the
lease cannot be updated.

so perhaps it's a lease timeout case..

Cheers,
Stefan

On 31/08/15 16:00, "Michael Dürig"  wrote:

>
>"The forked VM terminated without saying properly goodbye. VM crash or
>System.exit called ?" [2]. This happens quite often lately. See log
>files with -X option [1]. Not much information though. Any ideas what
>could be causing this?
>
>Michael
>
>[1] 
>https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/381/jdk=j
>dk1.8.0_11,label=Ubuntu,nsfixtures=SEGMENT_MK,profile=integrationTesting/c
>onsole
>
>[2]
>[ERROR] Failed to execute goal
>org.apache.maven.plugins:maven-failsafe-plugin:2.12.4:integration-test
>(default) on project oak-core: Execution default of goal
>org.apache.maven.plugins:maven-failsafe-plugin:2.12.4:integration-test
>failed: The forked VM terminated without saying properly goodbye. VM
>crash or System.exit called ? -> [Help 1]
>org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>execute goal 
>org.apache.maven.plugins:maven-failsafe-plugin:2.12.4:integration-test
>(default) on project oak-core: Execution default of goal
>org.apache.maven.plugins:maven-failsafe-plugin:2.12.4:integration-test
>failed: The forked VM terminated without saying properly goodbye. VM
>crash or System.exit called ?
>   at 
>org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java
>:224)
>   at 
>org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java
>:153)
>   at 
>org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java
>:145)
>   at 
>org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Li
>fecycleModuleBuilder.java:108)
>   at 
>org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Li
>fecycleModuleBuilder.java:76)
>   at 
>org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedB
>uilder.build(SingleThreadedBuilder.java:51)
>   at 
>org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStar
>ter.java:116)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
>62)
>   at 
>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
>pl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:483)
>   at 
>org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.
>java:289)
>   at 
>org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229
>)
>   at 
>org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launche
>r.java:415)
>   at 
>org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
>default of goal 
>org.apache.maven.plugins:maven-failsafe-plugin:2.12.4:integration-test
>failed: The forked VM terminated without saying properly goodbye. VM
>crash or System.exit called ?
>   at 
>org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuild
>PluginManager.java:144)
>   at 
>org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java
>:208)
>   ... 19 more
>Caused by: java.lang.RuntimeException: The forked VM terminated without
>saying properly goodbye. VM crash or System.exit called ?
>   at 
>org.apache.maven.plugin.surefire.booterclient.output.ForkClient.close(Fork
>Client.java:257)
>   at 
>org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter
>.java:301)
>   at 
>org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.
>java:116)
>   at 
>org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(Abst
>ractSurefireMojo.java:740)
>   at 
>org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAllProviders(
>AbstractSurefireMojo.java:682)
>   at 
>org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPrecondi
>tionsChecked(AbstractSurefireMojo.java:648)
>   at 
>org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSure
>fireMojo.java:586)
>   at 
>org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuild
>PluginManager.java:133)
>   ... 20 more
>
>
>On 31.8.15 3:56 , Apache Jenkins Server wrote:
>> The Apache Jenkins build system has built Apache Jackrabbit Oak matrix
>>(build #381)
>>
>> Status: Failure
>>
>> Check console output at

Re: Oak releases and profiles

2015-09-07 Thread Davide Giannella 
On 07/09/2015 11:08, Marcel Reutegger wrote:
> ...
> I would like to revert this change and run tests again
> with the pedantic profile. This ensures we check the release
> as documented in the README.md where users are instructed
> to run 'mvn clean install' or 'mvn clean install -PintegrationTesting'.
>

+1

We currently have a conf property in parent/pom.xml: surefire.skip.ut
(default false).

https://github.com/apache/jackrabbit-oak/blob/trunk/oak-parent/pom.xml#L72

You could reuse it, as we use it in jenkins and travis for having a
profile with unit test, and one with integrationTesting by having the
latter not re-running the unit test again.

If you want to change the property name, feel free to do so but you'll
have to change it in travis and jenkins as well.

Davide

Re: Lucene Property Index and OR condition

2015-09-07 Thread Chetan Mehrotra 
How did you performed the test? If you tested out with explain then
current code in 1.0/1.2 return misleading result and this got fixed in
trunk with OAK-2943. Technically Oak would convert the OR clause to a
union query and then each part of union should then be able to make
use of index.
Chetan Mehrotra


On Mon, Sep 7, 2015 at 6:36 PM, Davide Giannella  wrote:
> On 07/09/2015 14:32, Burkhard Pauli wrote:
>> ...
>> Question: Does the Lucene property index support or conditions? I tried
>> even with a oak property index without success.
>>
>
> I can be be totally wrong, so please take this carefully, but AFAIR
> lucene property index does not support ORs.
>
> This is mainly used for tests but should be valid for real-life as well
>
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/IndexPlanner.java#L452
>
> Davide
>
>

Re: Lucene Property Index and OR condition

2015-09-07 Thread Burkhard Pauli 
Hi Chetan,

Thanks for your feedback. It was tested with version 1.0.15 which is part
of AEM 6.0 SP2. Good to know that this is fixed now.

Are you aware of any HF for version 1.0.x?

Thanks
Burkhard

On Mon, Sep 7, 2015 at 5:41 PM, Chetan Mehrotra 
wrote:

> How did you performed the test? If you tested out with explain then
> current code in 1.0/1.2 return misleading result and this got fixed in
> trunk with OAK-2943. Technically Oak would convert the OR clause to a
> union query and then each part of union should then be able to make
> use of index.
> Chetan Mehrotra
>
>
> On Mon, Sep 7, 2015 at 6:36 PM, Davide Giannella 
> wrote:
> > On 07/09/2015 14:32, Burkhard Pauli wrote:
> >> ...
> >> Question: Does the Lucene property index support or conditions? I tried
> >> even with a oak property index without success.
> >>
> >
> > I can be be totally wrong, so please take this carefully, but AFAIR
> > lucene property index does not support ORs.
> >
> > This is mainly used for tests but should be valid for real-life as well
> >
> >
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/IndexPlanner.java#L452
> >
> > Davide
> >
> >
>



-- 
––
Burkhard Pauli
Bötzowstr. 13 | 10407 Berlin
Fon 030. 648 315 73 | Mobil 0151. 227 337 53
–-

Re: Lucene Property Index and OR condition

2015-09-07 Thread Davide Giannella 
On 07/09/2015 14:32, Burkhard Pauli wrote:
> ...
> Question: Does the Lucene property index support or conditions? I tried
> even with a oak property index without success.
>

I can be be totally wrong, so please take this carefully, but AFAIR
lucene property index does not support ORs.

This is mainly used for tests but should be valid for real-life as well

https://github.com/apache/jackrabbit-oak/blob/trunk/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/IndexPlanner.java#L452

Davide

[Oak origin/1.0] Apache Jackrabbit Oak matrix - Build # 398 - Still Failing

2015-09-07 Thread Apache Jenkins Server 
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build 
#398)

Status: Still Failing

Check console output at 
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/398/ to view 
the results.

Changes:
[mreutegg] OAK-3313: Many tests leak DocumentNodeStore instances

 

Test results:
12 tests failed.
FAILED:  org.apache.jackrabbit.oak.jcr.query.SuggestTest.testSuggestSql

Error Message:
expected:<[[{term=in 2015 a red fox is still a fox,weight=1}, {term=in 2015 my 
fox is red, like mike's fox and john's fox,weight=1}]]> but was:<[]>

Stack Trace:
junit.framework.ComparisonFailure: expected:<[[{term=in 2015 a red fox is still 
a fox,weight=1}, {term=in 2015 my fox is red, like mike's fox and john's 
fox,weight=1}]]> but was:<[]>
at junit.framework.Assert.assertEquals(Assert.java:85)
at junit.framework.Assert.assertEquals(Assert.java:91)
at 
org.apache.jackrabbit.oak.jcr.query.SuggestTest.testSuggestSql(SuggestTest.java:50)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at 
org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:464)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)


FAILED:  org.apache.jackrabbit.oak.jcr.query.SuggestTest.testSuggestXPath

Error Message:
expected:<[[{term=in 2015 a red fox is still a fox,weight=1}, {term=in 2015 my 
fox is red, like mike's fox and john's fox,weight=1}]]> but was:<[]>

Stack Trace:
junit.framework.ComparisonFailure: expected:<[[{term=in 2015 a red fox is still 
a fox,weight=1}, {term=in 2015 my fox is red, like mike's fox and john's 
fox,weight=1}]]> but was:<[]>
at junit.framework.Assert.assertEquals(Assert.java:85)
at junit.framework.Assert.assertEquals(Assert.java:91)
at 
org.apache.jackrabbit.oak.jcr.query.SuggestTest.testSuggestXPath(SuggestTest.java:67)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at 
org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:464)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at

[Oak origin/1.2] Apache Jackrabbit Oak matrix - Build # 397 - Still Failing

2015-09-07 Thread Apache Jenkins Server 
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build 
#397)

Status: Still Failing

Check console output at 
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/397/ to view 
the results.

Changes:
[mreutegg] OAK-3313: Many tests leak DocumentNodeStore instances

 

Test results:
4 tests failed.
FAILED:  
org.apache.jackrabbit.oak.security.authentication.ldap.LdapProviderTest.testGetUserProperties

Error Message:
 Expected: <{uid=hhornblo, mail=hhorn...@royalnavy.mod.uk, givenname=Horatio, 
description=Capt. Horatio Hornblower, R.N, sn=Hornblower, cn=Horatio 
Hornblower, objectclass=[top, person, organizationalPerson, inetOrgPerson]}>
  got: <{uid=hhornblo, mail=hhorn...@royalnavy.mod.uk, sn=Hornblower, 
cn=Horatio Hornblower, description=Capt. Horatio Hornblower, R.N, 
givenname=Horatio, objectclass=[organizationalPerson, person, inetOrgPerson, 
top]}> 

Stack Trace:
java.lang.AssertionError: 
Expected: <{uid=hhornblo, mail=hhorn...@royalnavy.mod.uk, givenname=Horatio, 
description=Capt. Horatio Hornblower, R.N, sn=Hornblower, cn=Horatio 
Hornblower, objectclass=[top, person, organizationalPerson, inetOrgPerson]}>
 got: <{uid=hhornblo, mail=hhorn...@royalnavy.mod.uk, sn=Hornblower, 
cn=Horatio Hornblower, description=Capt. Horatio Hornblower, R.N, 
givenname=Horatio, objectclass=[organizationalPerson, person, inetOrgPerson, 
top]}>

at org.junit.Assert.assertThat(Assert.java:780)
at org.junit.Assert.assertThat(Assert.java:738)
at 
org.apache.jackrabbit.oak.security.authentication.ldap.LdapProviderTest.testGetUserProperties(LdapProviderTest.java:187)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)


REGRESSION:  org.apache.jackrabbit.oak.jcr.OrderableNodesTest.setPrimaryType[0]

Error Message:
Failed to register node types.

Stack Trace:
javax.jcr.InvalidItemStateException: Failed to register node types.
at 
org.apache.jackrabbit.oak.api.CommitFailedException.asRepositoryException(CommitFailedException.java:239)
at 
org.apache.jackrabbit.oak.plugins.nodetype.write.ReadWriteNodeTypeManager.registerNodeTypes(ReadWriteNodeTypeManager.java:156)
at