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

2016-10-20 Thread Apache Jenkins Server
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build 
#1227)

Status: Still Failing

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

Changes:
[reschke] OAK-4964: UpdateOp.set("_id", ...) should do a sanity check on the id

 

Test results:
1 tests failed.
FAILED:  
org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexQueryTest.sql2

Error Message:
Query took too long: select a.[jcr:path] from [nt:base] as a   left outer join 
[nt:base] as b on ischildnode(b, a)   where name(b) = 'b' took 12481 ms

Stack Trace:
java.lang.AssertionError: Query took too long: select a.[jcr:path] from 
[nt:base] as a
  left outer join [nt:base] as b on ischildnode(b, a)
  where name(b) = 'b' took 12481 ms
at org.junit.Assert.fail(Assert.java:88)
at 
org.apache.jackrabbit.oak.query.AbstractQueryTest.executeQuery(AbstractQueryTest.java:280)
at 
org.apache.jackrabbit.oak.query.AbstractQueryTest.executeQuery(AbstractQueryTest.java:255)
at 
org.apache.jackrabbit.oak.query.AbstractQueryTest.executeQuery(AbstractQueryTest.java:251)
at 
org.apache.jackrabbit.oak.query.AbstractQueryTest.test(AbstractQueryTest.java:187)
at 
org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexQueryTest.sql2(LuceneIndexQueryTest.java:93)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
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:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
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)




Re: Builds timing out: ubuntu-2 extremely slow

2016-10-20 Thread Michael Dürig


Thanks, looks better now. The builds work again on ubuntu-2.

Michael

On 20.10.16 6:37 , Pono Takamori wrote:

This node had some hung jobs, so I've rebooted it and hopefully it can
be speedier now.

Cheers,
-Pono from Infra

On Wed, Oct 19, 2016 at 3:49 AM, Michael Dürig  wrote:


Hi,

Our builds regularly time out when assigned to the ubuntu-2 slave. Is there
anything wrong with that particular slave? Any way to exclude it so we can
get back to stable builds?

For comparison:

[INFO] Oak Core . SUCCESS [04:46 min]
[INFO] Oak Core . SUCCESS [33:00 min]

The former is on jenkins-test-689 and completed after 21 minutes. The latter
is on ubuntu-2 and timed out after 2 hours.

See
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1217/jdk=JDK%201.8%20(latest),label=Ubuntu,nsfixtures=DOCUMENT_NS,profile=unittesting/
and
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1218/jdk=JDK%201.8%20(latest),label=Ubuntu,nsfixtures=DOCUMENT_NS,profile=unittesting/

Michael


Re: Builds timing out: ubuntu-2 extremely slow

2016-10-20 Thread Pono Takamori
This node had some hung jobs, so I've rebooted it and hopefully it can
be speedier now.

Cheers,
-Pono from Infra

On Wed, Oct 19, 2016 at 3:49 AM, Michael Dürig  wrote:
>
> Hi,
>
> Our builds regularly time out when assigned to the ubuntu-2 slave. Is there
> anything wrong with that particular slave? Any way to exclude it so we can
> get back to stable builds?
>
> For comparison:
>
> [INFO] Oak Core . SUCCESS [04:46 min]
> [INFO] Oak Core . SUCCESS [33:00 min]
>
> The former is on jenkins-test-689 and completed after 21 minutes. The latter
> is on ubuntu-2 and timed out after 2 hours.
>
> See
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1217/jdk=JDK%201.8%20(latest),label=Ubuntu,nsfixtures=DOCUMENT_NS,profile=unittesting/
> and
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1218/jdk=JDK%201.8%20(latest),label=Ubuntu,nsfixtures=DOCUMENT_NS,profile=unittesting/
>
> Michael


Oak 1.5.13 release plan

2016-10-20 Thread Davide Giannella
Hello team,

I'm planning to cut Oak 1.5.13 on Monday 24th.

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 Segment Tar version 0.0.16

2016-10-20 Thread Alex Parvulescu
[X] +1 Approve the release

On Thu, Oct 20, 2016 at 2:08 PM, Francesco Mari 
wrote:

> Hi,
>
> We solved 19 issues in this release:
> https://issues.apache.org/jira/browse/OAK/fixforversion/12338072
>
> There are still some outstanding issues:
> https://issues.apache.org/jira/browse/OAK/component/12329487
>
> Staging repository:
> https://repository.apache.org/content/repositories/
> orgapachejackrabbit-1199
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/jackrabbit/oak/trunk/
> check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1199 /tmp/oak-staging
>
> Please vote to approve this release:
>
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>


Re: On adding new APIs

2016-10-20 Thread Michael Dürig



On 20.10.16 2:21 , Bertrand Delacretaz wrote:

On Thu, Oct 20, 2016 at 2:02 PM, Michael Marth  wrote:

...So I have a proposal: when a new public API is added the developer should 
drop an
email with subject tag [REVIEW] onto the dev list, so that others are aware and 
can
chime in if needed...


The Oak team can also just decide that new APIs are to be handled in
R-T-C mode instead of C-T-R.

It's kind of the same thing but using standard Apache terminology ;-)



But then all strictness of RTC is not necessary IMO. In many cases it is 
easier to commit, review and iterate.


My main concern is ensuring API changes get a broad enough review 
involving enough members of the team. The aim is to avoid island 
solutions driven by the need to fix a single issue in one place. We need 
to ensure the APIs evolve in a consistent and generally useful way. A 
good way of doing this is to involve other people in the discussion who 
work in different areas as this would usually widen the scope.


My proposal would be to still keep it informal but involve the dev list 
a bit more explicitly by tagging the subject either with [API] or 
[REVIEW] or even [RTC] if so desired. These tags should signal other 
team members to get involved even though the poster usually works on 
something outside one's area of expertise.


Michael



Re: [VOTE] Release Apache Jackrabbit Oak Segment Tar version 0.0.16

2016-10-20 Thread Davide Giannella

[X] +1 Approve the release


Davide


Re: On adding new APIs

2016-10-20 Thread Davide Giannella
On 20/10/2016 13:02, Michael Marth wrote:
> developer should drop an email with subject tag [REVIEW]

ok for the email, but it should point to a ticket in jira where the
discussion would happen.

Davide




Re: On adding new APIs

2016-10-20 Thread Thomas Mueller
Hi,

I would prefer C-T-R (commit, then review), because it reduces
bureaucracy. Except for changes just before a major release (when there is
little time to und or change things).


+1 to [REVIEW] emails. In my view, this should include new configuration
and new features. Basically all "important" user-visible behavior changes.
Sure, it's hard to say what is important and what is not.

Regards,
Thomas




On 20/10/16 14:21, "Bertrand Delacretaz"  wrote:

>On Thu, Oct 20, 2016 at 2:02 PM, Michael Marth  wrote:
>> ...So I have a proposal: when a new public API is added the developer
>>should drop an
>> email with subject tag [REVIEW] onto the dev list, so that others are
>>aware and can
>> chime in if needed...
>
>The Oak team can also just decide that new APIs are to be handled in
>R-T-C mode instead of C-T-R.
>
>It's kind of the same thing but using standard Apache terminology ;-)
>
>-Bertrand



Re: [VOTE] Release Apache Jackrabbit Oak Segment Tar version 0.0.16

2016-10-20 Thread Francesco Mari
+1

2016-10-20 14:17 GMT+02:00 Michael Dürig :
>
>
> On 20.10.16 2:08 , Francesco Mari wrote:
>>
>>   [X] +1 Approve the release
>
>
> Michael


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

2016-10-20 Thread Apache Jenkins Server
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build 
#1226)

Status: Still Failing

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

Changes:
No changes
 

Test results:
16 tests failed.
FAILED:  org.apache.jackrabbit.j2ee.TomcatIT.testTomcat

Error Message:
expected: but was:

Stack Trace:
junit.framework.ComparisonFailure: expected: but 
was:
at junit.framework.Assert.assertEquals(Assert.java:100)
at junit.framework.Assert.assertEquals(Assert.java:107)
at junit.framework.TestCase.assertEquals(TestCase.java:269)
at org.apache.jackrabbit.j2ee.TomcatIT.testTomcat(TomcatIT.java:103)
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 junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:252)
at junit.framework.TestSuite.run(TestSuite.java:247)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
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)


FAILED:  
org.apache.jackrabbit.oak.plugins.segment.standby.ExternalPrivateStoreIT.testProxySkippedBytes

Error Message:
expected:<{ root = { ... } }> but was:<{ root : { } }>

Stack Trace:
java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { } }>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
org.apache.jackrabbit.oak.plugins.segment.standby.DataStoreTestBase.useProxy(DataStoreTestBase.java:193)
at 
org.apache.jackrabbit.oak.plugins.segment.standby.DataStoreTestBase.testProxySkippedBytes(DataStoreTestBase.java:127)
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:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at 

Re: svn commit: r1765583 - in /jackrabbit/oak/trunk: oak-core/src/main/java/org/apache/jackrabbit/oak/api/jmx/ oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/property/strategy/ oak-cor

2016-10-20 Thread Julian Sedding
> -@Version("4.0.0")
> +@Version("5.0.0")
>  @Export(optional = "provide:=true")
>  package org.apache.jackrabbit.oak.api.jmx;

I think we could get away with increasing this to 4.1.0 if we can
annotate QueryEngineSettingsMBean with @ProviderType. I.e. we don't
expect API consumers to  implement QueryEngineSettingsMBean and
therefore the API change is irrelevant for them.

WDYT?

Regards
Julian



On Wed, Oct 19, 2016 at 2:20 PM,   wrote:
> Author: thomasm
> Date: Wed Oct 19 12:20:56 2016
> New Revision: 1765583
>
> URL: http://svn.apache.org/viewvc?rev=1765583=rev
> Log:
> OAK-4888 Warn or fail queries above a configurable cost value
>
> Added:
> 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/query/QueryOptions.java
> Modified:
> 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/api/jmx/QueryEngineSettingsMBean.java
> 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/api/jmx/package-info.java
> 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/property/strategy/ContentMirrorStoreStrategy.java
> 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/query/Query.java
> 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/query/QueryEngineSettings.java
> 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/query/QueryEngineSettingsMBeanImpl.java
> 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/query/QueryImpl.java
> 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/query/SQL2Parser.java
> 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/query/UnionQueryImpl.java
> 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/query/xpath/Statement.java
> 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/query/xpath/XPathToSQL2Converter.java
> 
> jackrabbit/oak/trunk/oak-core/src/test/java/org/apache/jackrabbit/oak/query/SQL2ParserTest.java
> 
> jackrabbit/oak/trunk/oak-core/src/test/java/org/apache/jackrabbit/oak/query/XPathTest.java
> 
> jackrabbit/oak/trunk/oak-jcr/src/test/java/org/apache/jackrabbit/oak/jcr/query/QueryTest.java
>
> Modified: 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/api/jmx/QueryEngineSettingsMBean.java
> URL: 
> http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/api/jmx/QueryEngineSettingsMBean.java?rev=1765583=1765582=1765583=diff
> ==
> --- 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/api/jmx/QueryEngineSettingsMBean.java
>  (original)
> +++ 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/api/jmx/QueryEngineSettingsMBean.java
>  Wed Oct 19 12:20:56 2016
> @@ -51,4 +51,19 @@ public interface QueryEngineSettingsMBea
>   */
>  void setLimitReads(long limitReads);
>
> +/**
> + * Whether queries that don't use an index will fail (throw an 
> exception).
> + * The default is false.
> + *
> + * @return true if they fail
> + */
> +boolean getFailTraversal();
> +
> +/**
> + * Set whether queries that don't use an index will fail (throw an 
> exception).
> + *
> + * @param failTraversal the new value for this setting
> + */
> +void setFailTraversal(boolean failTraversal);
> +
>  }
>
> Modified: 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/api/jmx/package-info.java
> URL: 
> http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/api/jmx/package-info.java?rev=1765583=1765582=1765583=diff
> ==
> --- 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/api/jmx/package-info.java
>  (original)
> +++ 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/api/jmx/package-info.java
>  Wed Oct 19 12:20:56 2016
> @@ -15,7 +15,7 @@
>   * limitations under the License.
>   */
>
> -@Version("4.0.0")
> +@Version("5.0.0")
>  @Export(optional = "provide:=true")
>  package org.apache.jackrabbit.oak.api.jmx;
>
>
> Modified: 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/property/strategy/ContentMirrorStoreStrategy.java
> URL: 
> http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/property/strategy/ContentMirrorStoreStrategy.java?rev=1765583=1765582=1765583=diff
> ==
> --- 
> jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/property/strategy/ContentMirrorStoreStrategy.java
>  (original)
> +++ 
> 

Re: On adding new APIs

2016-10-20 Thread Bertrand Delacretaz
On Thu, Oct 20, 2016 at 2:02 PM, Michael Marth  wrote:
> ...So I have a proposal: when a new public API is added the developer should 
> drop an
> email with subject tag [REVIEW] onto the dev list, so that others are aware 
> and can
> chime in if needed...

The Oak team can also just decide that new APIs are to be handled in
R-T-C mode instead of C-T-R.

It's kind of the same thing but using standard Apache terminology ;-)

-Bertrand


Re: [VOTE] Release Apache Jackrabbit Oak Segment Tar version 0.0.16

2016-10-20 Thread Michael Dürig



On 20.10.16 2:08 , Francesco Mari wrote:

  [X] +1 Approve the release


Michael


[VOTE] Release Apache Jackrabbit Oak Segment Tar version 0.0.16

2016-10-20 Thread Francesco Mari
Hi,

We solved 19 issues in this release:
https://issues.apache.org/jira/browse/OAK/fixforversion/12338072

There are still some outstanding issues:
https://issues.apache.org/jira/browse/OAK/component/12329487

Staging repository:
https://repository.apache.org/content/repositories/orgapachejackrabbit-1199

You can use this UNIX script to download the release and verify the signatures:
http://svn.apache.org/repos/asf/jackrabbit/oak/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1199 /tmp/oak-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.


On adding new APIs

2016-10-20 Thread Michael Marth
Hi all,

I had a discussion with Michael Dürig about adding new Oak-specific APIs for 
public consumption. There is a concern that these might be too “ad-hoc” and 
might come back to bite us later.
OTOH I would not like to add too much process or ceremony.
So I have a proposal: when a new public API is added the developer should drop 
an email with subject tag [REVIEW] onto the dev list, so that others are aware 
and can chime in if needed.

WDYT?
Michael


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

2016-10-20 Thread Apache Jenkins Server
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build 
#1225)

Status: Still Failing

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

Changes:
[frm] OAK-4958 - Remove unused method from DataStoreTestBase

[frm] OAK-4963 - Ensure proper finalization of test resources

[chetanm] OAK-1312 - Bundle nodes into a document

 

Test results:
1 tests failed.
FAILED:  org.apache.jackrabbit.j2ee.TomcatIT.testTomcat

Error Message:
expected: but was:

Stack Trace:
junit.framework.ComparisonFailure: expected: but 
was:
at junit.framework.Assert.assertEquals(Assert.java:100)
at junit.framework.Assert.assertEquals(Assert.java:107)
at junit.framework.TestCase.assertEquals(TestCase.java:269)
at org.apache.jackrabbit.j2ee.TomcatIT.testTomcat(TomcatIT.java:103)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:252)
at junit.framework.TestSuite.run(TestSuite.java:247)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
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:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
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)




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

2016-10-20 Thread Apache Jenkins Server
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build 
#1224)

Status: Still Failing

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

Changes:
No changes
 

Test results:
1 tests failed.
FAILED:  org.apache.jackrabbit.j2ee.TomcatIT.testTomcat

Error Message:
expected: but was:

Stack Trace:
junit.framework.ComparisonFailure: expected: but 
was:
at junit.framework.Assert.assertEquals(Assert.java:100)
at junit.framework.Assert.assertEquals(Assert.java:107)
at junit.framework.TestCase.assertEquals(TestCase.java:269)
at org.apache.jackrabbit.j2ee.TomcatIT.testTomcat(TomcatIT.java:103)
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 junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:252)
at junit.framework.TestSuite.run(TestSuite.java:247)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
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)