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/3742
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
Tests in error:
testConcurrentGC(org.apache.jackrabbit.mk.store.DefaultRevisionStoreTest):
java.util.concurrent.ExecutionException:
org.apache.jackrabbit.mk.store.NotFoundException:
0767a71c1e145e6cc9ac227c9ec021743f30dbb1
On Tue, Nov 19, 2013 at 4:12 PM, wrote:
> The Buildbot has detected
Build Update for apache/jackrabbit-oak
-
Build: #2706
Status: Broken
Duration: 215 seconds
Commit: a0bf49cc5a2344abfb4e84a15ed562e9b9f94e25 (trunk)
Author: Michael Duerig
Message: OAK-1200 occasional test failure in
org.apache.jackrabbit.mk.store.DefaultRevisi
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/3743
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stam
Tests in error:
testConcurrentGC(org.apache.jackrabbit.mk.store.DefaultRevisionStoreTest):
java.util.concurrent.ExecutionException:
org.apache.jackrabbit.mk.store.NotFoundException:
8b88bcab746332af93a940bb9d95c8c235ae3473
On Tue, Nov 19, 2013 at 4:28 PM, Travis CI wrote:
> Build Update for ap
Build Update for apache/jackrabbit-oak
-
Build: #2707
Status: Fixed
Duration: 2275 seconds
Commit: 044ce348763e5bfc21d9e65635db5616118721b7 (trunk)
Author: Michael Duerig
Message: OAK-1200: occasional test failure in
org.apache.jackrabbit.mk.store.DefaultRevis
Build Update for apache/jackrabbit-oak
-
Build: #2709
Status: Fixed
Duration: 2121 seconds
Commit: e5146736442ab98e829318925ae3f98faeb996fe (trunk)
Author: Michael Duerig
Message: OAK-1133: Observation listener PLUS
Evaluate trivial filters on instantiation
gi
Hi,
On Tue, Nov 19, 2013 at 1:57 AM, Chetan Mehrotra
wrote:
> On some systems running on Oak (on Windows) where lots of nodes get
> created we are seeing high RAM usage. The Java process memory (shown
> directly under task manager. See note on Working Set below) remains
> within expected range bu
On Tue, Nov 19, 2013 at 11:29 PM, Jukka Zitting wrote:
> Hmm, I wonder if we do have a problem here or if the system is just
> working as designed.
Thats my thinking as well and hence wanted to discuss this on DL
first. The system here was being subjected to some DAM related tests
and quite a few
