The Buildbot has detected a new failure on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/4768
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source Sta
The Buildbot has detected a restored build on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/4767
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
The Buildbot has detected a new failure on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/4766
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source Sta
Hi,
I recently encountered a bug where someone created an index definition
in the initial content, that contains a property name with a namespace
that was never registered. something like:
IndexUtils.createIndexDefinition(builder, "test", true, false,
singleton("foo:testproperty"), null);
the in
The Buildbot has detected a restored build on builder oak-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/4582
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stam
The Buildbot has detected a new failure on builder oak-trunk while building ASF
Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/4581
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
The Buildbot has detected a restored build on builder oak-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/4580
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stam
The Buildbot has detected a restored build on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/4760
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
Hi,
I created a test that created a node structure with 10k node, each
having 1 ACL and 1 ACE for the everyone principle.
then, with concurrent reader sessions, I read the nodes randomly.
Benchmarks: ConcurrentEveryoneACLTest (oak 0.19-SNAPSHOT with everyone cache)
Fixtures: Oak-Tar
Runtime: 5
Nu
Hi,
On Wed, Mar 5, 2014 at 2:33 PM, wrote:
> http://ci.apache.org/builders/oak-trunk/builds/4579
Running org.apache.jackrabbit.oak.plugins.document.ConcurrentConflictTest
Tests run: 2, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 0.415
sec <<< FAILURE!
concurrentUpdates(org.apache.jackrab
Build Update for apache/jackrabbit-oak
-
Build: #3585
Status: Errored
Duration: 3002 seconds
Commit: 7f4e3f8400f0bc51aa83c0edc4ad0135856863fe (trunk)
Author: Tobias Bocanegra
Message: @trivial adding another test
git-svn-id: https://svn.apache.org/repos/asf/ja
The Buildbot has detected a new failure on builder oak-trunk while building ASF
Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/4579
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
The Buildbot has detected a new failure on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/4759
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source Sta
On 2014-03-05 11:34, Alex Parvulescu wrote:
...
[ ] +1 Release this package as Apache Jackrabbit Oak 0.18
[ ] -1 Do not release this package because...
My vote is +1
best,
alex
[X] +1 Release this package as Apache Jackrabbit Oak 0.18
hi
>I looked at the problem again. Removing the mod-count improves
>concurrency when writing ACLs a lot (about 2 times faster with mongo
>and 20 threads). the read-performance does not suffer much with the
>current tests - but then the tests might not be accurate. the
>permission cache is only use
The Buildbot has detected a restored build on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/4758
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
The Buildbot has detected a restored build on builder oak-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/4574
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stam
Hi,
I looked at the problem again. Removing the mod-count improves
concurrency when writing ACLs a lot (about 2 times faster with mongo
and 20 threads). the read-performance does not suffer much with the
current tests - but then the tests might not be accurate. the
permission cache is only used to
Hi,
On Wed, Mar 5, 2014 at 10:07 AM, wrote:
> Full details are available at:
> http://ci.apache.org/builders/oak-trunk-win7/builds/4756
The problem was:
Running org.apache.jackrabbit.oak.spi.commit.BackgroundObserverTest
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.031
se
The Buildbot has detected a new failure on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/4756
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source Sta
The Buildbot has detected a new failure on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/4755
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source Sta
This looks similar than what we have been seeing earlier today:
concurrent[2](org.apache.jackrabbit.oak.jcr.ConcurrentFileOperationsTest)
Time elapsed: 0.181 sec <<< ERROR!
java.lang.Exception: session-0
jcr:primaryType: nt:unstructured
file-0.bin
jcr:created: 2014-03-05T14:06:09.722Z
The Buildbot has detected a new failure on builder oak-trunk while building ASF
Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/4573
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
> Please vote on releasing this package as Apache Jackrabbit Oak 0.18.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
+1 Release this package as Apache Jackrabbit Oak 0.18
All checks OK.
Regards
Marcel
Build Update for apache/jackrabbit-oak
-
Build: #3579
Status: Passed
Duration: 2298 seconds
Commit: 69db4072c31277c37ea7d3f73ef323c26b0da713 (trunk)
Author: Davide Giannella
Message: OAK-1263 another round of formatting
View the changeset: https://github.com/a
On 05/03/2014 10:34, Alex Parvulescu wrote:
> [ ] +1 Release this package as Apache Jackrabbit Oak 0.18
> [ ] -1 Do not release this package because...
+1
Build Update for apache/jackrabbit-oak
-
Build: #3577
Status: Errored
Duration: 3002 seconds
Commit: 64d93bd2dc1def2ab1c38716437306d59aa81ad7 (trunk)
Author: Michael Duerig
Message: OAK-1491: ObservationTest failure on Windows
Add some instrumentation to test c
On 5.3.14 11:34 , Alex Parvulescu wrote:
[X] +1 Release this package as Apache Jackrabbit Oak 0.18
Michael
Build Update for apache/jackrabbit-oak
-
Build: #3576
Status: Passed
Duration: 2315 seconds
Commit: 8de6dc6ab49eaa430492d6f1500ddafe0f716d90 (jackrabbit-oak-0.18)
Author: Alexandru Parvulescu
Message: [maven-release-plugin] copy for tag jackrabbit-oak-0.18
gi
A candidate for the Jackrabbit Oak 0.18 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/oak/0.18/
The release candidate is a zip archive of the sources in:
https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-0.18/
The SHA1 checksum of the archive
The Buildbot has detected a restored build on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/4750
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
The Buildbot has detected a new failure on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/4749
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source Sta
hmm, looks like the test tries to bootstrap the repository even though it
already happened in the @Before method...
Regards
Marcel
> Haven't seen this before:
>
> rebaseVisibility(org.apache.jackrabbit.oak.jcr.ConcurrentAddNodesClusterIT
> )
> Time elapsed: 11.26 sec <<< ERROR!
> java.lang.R
Hi,
> FWIW DocumentNodeStore maintains a property '_modCount' on a per node
> basis and it can possibly be exposed as part of NodeStore as a hidden
> property.
the _modCount is not sufficiently accurate. it does not take pending updates
of the _lastRev into account. we'd have to use DocumentNod
Haven't seen this before:
rebaseVisibility(org.apache.jackrabbit.oak.jcr.ConcurrentAddNodesClusterIT)
Time elapsed: 11.26 sec <<< ERROR!
java.lang.RuntimeException:
org.apache.jackrabbit.oak.api.CommitFailedException: OakMerge0001:
OakMerge0001: Failed to merge changes to the underlying sto
Build Update for apache/jackrabbit-oak
-
Build: #3572
Status: Broken
Duration: 1329 seconds
Commit: fde3dc1cffb120968abac8999a1a15aeb1c91b1e (trunk)
Author: Michael Duerig
Message: OAK-1429: Slow event listeners do not scale as expected
Enable slowListener test
Hi,
My suggestion would be to (additionally or only) expose the current
cluster node id in some way.
That way, oak-core (mainly hooks I guess; for example index
implementations) can create properties and nodes that are known to not
conflict with changes of other cluster nodes.
Regards,
Thomas
On 05/03/2014 00:58, Jukka Zitting wrote:
> I remember myself searching at least for rep:AccessControllable on
> various occasions. It's a quick and easy way to locate ACLs within a
> repository.
I searched many times in CQ for the rep:ACL for packaging ACLs and
moving them from one environment to
38 matches
Mail list logo