Build Update for apache/jackrabbit-oak
-
Build: #3209
Status: Broken
Duration: 1874 seconds
Commit: 97b2a36af5139ebe673eb86fa6218bc34365fe84 (trunk)
Author: Jukka Zitting
Message: OAK-1332: Large number of changes to the same node can fill
observation queue
I
Build Update for apache/jackrabbit-oak
-
Build: #3208
Status: Fixed
Duration: 2569 seconds
Commit: d420ce0d792902a6c7ff74764c54fdf8c55470e6 (trunk)
Author: Jukka Zitting
Message: OAK-1332: Large number of changes to the same node can fill
observation queue
Op
Build Update for apache/jackrabbit-oak
-
Build: #3207
Status: Fixed
Duration: 2492 seconds
Commit: 9c6d43e8523629dbe1d3faf4a6477d7d75608421 (trunk)
Author: Jukka Zitting
Message: OAK-1332: Large number of changes to the same node can fill
observation queue
Fi
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/4243
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stam
Hi,
On Tue, Jan 28, 2014 at 9:04 PM, wrote:
> 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/4242
Oops, my bad. Fixing it now.
BR,
Jukka Zitting
Build Update for apache/jackrabbit-oak
-
Build: #3206
Status: Broken
Duration: 1453 seconds
Commit: ce01d677bc3c852171c90294c43351d61d598e41 (trunk)
Author: Jukka Zitting
Message: OAK-1332: Large number of changes to the same node can fill
observation queue
I
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/4242
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
Hi,
On Tue, Jan 28, 2014 at 2:32 PM, Tobias Bocanegra wrote:
> I also think that the amount of exported packages is very large. It
> looks like we didn't really know how to modularize oak and just
> exported basically everything :-)
That's a pretty broad statement. Yes, there are a few cases whe
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/4239
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/4238
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/4237
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stam
On Tue, Jan 28, 2014 at 11:32 AM, Jukka Zitting wrote:
> Hi,
>
> On Tue, Jan 28, 2014 at 2:20 PM, Tobias Bocanegra wrote:
>> as i mentioned before. it's not a branch nor a tag of an official
>> release, but merely a place to record that I intended to use a 0.15.2
>> version of oak-core.
>
> I thi
Hi,
On Tue, Jan 28, 2014 at 2:20 PM, Tobias Bocanegra wrote:
> as i mentioned before. it's not a branch nor a tag of an official
> release, but merely a place to record that I intended to use a 0.15.2
> version of oak-core.
I think it would be clearer if you moved it from tags/ to branches/,
as
Hi,
On Tue, Jan 28, 2014 at 1:54 AM, Chetan Mehrotra
wrote:
> On Tue, Jan 28, 2014 at 7:41 AM, wrote:
>> + org.apache.jackrabbit.oak;version="0.15.0",
>> + org.apache.jackrabbit.oak.api;version="0.15.0",
>> + org.apache.jackrabbit.oak.api.jmx;version="0.15
Hi,
On Tue, Jan 28, 2014 at 1:11 AM, Alex Parvulescu
wrote:
> Hi,
>
> Shouldn't these changes go into trunk directly? I only see then on the new
> branch.
no, they are in trunk. I added them here:
https://svn.apache.org/viewvc?view=revision&revision=1560563
> Second, I did not see any kind of di
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/4236
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
Hi there,
with the current trunk, I occasionally get the test failure below
(oak-core):
---
Test set: org.apache.jackrabbit.oak.plugins.document.RevisionTest
Hi,
On Tue, Jan 28, 2014 at 9:30 AM, Alex Parvulescu
wrote:
> This assumption was challenged via OAK-1357 with the idea that the MongoDB
> backup can already produce consistent (non-blocking) backups so there's
> nothing to be done in this area.
"MMS Backup offers point in time recovery of Mongo
Hi,
re
> This assumption was challenged via OAK-1357 with the idea that the MongoDB
> backup can already produce consistent (non-blocking) backups so there's
> nothing to be done in this area. Also restoring means only replacing the
> old db with the backup one.
I am not sure if MongoDB is able t
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/4232
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stam
Hi,
I'm back trying to gather some feedback from the people involved in the
MongoDB store impl.
This is about creating a backup of the current repository using a native
backup tool, a tool that is running at databasel level.
It was my understanding that if you run a (non blocking) backup at any
g
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/4231
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
Build Update for apache/jackrabbit-oak
-
Build: #3185
Status: Passed
Duration: 2606 seconds
Commit: 952503582d960db1f82eb4f2ee91badfd65c182f (trunk)
Author: Angela Schreiber
Message: OAK-919: test-case
OAK-915: enable tests
git-svn-id: https://svn.apache.org/r
Build Update for apache/jackrabbit-oak
-
Build: #3184
Status: Passed
Duration: 2285 seconds
Commit: a555fd75bf7eca02bed29024678f88236f99abd7 (trunk)
Author: Marcel Reutegger
Message: OAK-1360: Rename o.a.j.o.plugins.mongomk to o.a.j.o.plugins.document
- move Do
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/4225
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stam
the build output says:
[INFO] --- findbugs-maven-plugin:2.5.2:findbugs (findbugs) @ oak-mk-remote ---
[INFO] Fork Value is true
No output has been received in the last 10 minutes, this potentially indicates
a stalled build or something wrong with the build itself.
The build has been terminated
Tests in error:
testRegisterCustomPrivileges(org.apache.jackrabbit.oak.jcr.security.privilege.PrivilegeRegistrationTest):
Java heap space
happened after I started to refactore the mongomk packages.
Let's see if the build still fails when I'm finished with my changes...
Regards
Marcel
Build Update for apache/jackrabbit-oak
-
Build: #3183
Status: Errored
Duration: 783 seconds
Commit: 8a335b87c058de3604809f92ce9faa8eb995ce2c (trunk)
Author: Marcel Reutegger
Message: OAK-1360: Rename o.a.j.o.plugins.mongomk to o.a.j.o.plugins.document
- rename
On Tue, Jan 28, 2014 at 7:41 AM, wrote:
> + org.apache.jackrabbit.oak;version="0.15.0",
> + org.apache.jackrabbit.oak.api;version="0.15.0",
> + org.apache.jackrabbit.oak.api.jmx;version="0.15.0",
We should version packages independent of Oak release version
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/4224
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
Hi,
Shouldn't these changes go into trunk directly? I only see then on the new
branch.
Second, I did not see any kind of discussion/announcement related to this
new branch. We create releases every 2 weeks, couldn't this have waited a
few days?
best,
alex
On Tue, Jan 28, 2014 at 6:26 AM, Tob
Hi,
>Are there better ways of doing this? for example as suggested by Thomas to
>use the repository.xml to read the datastore configuration.
Yes, I think that would be the most user friendly approach, specially for
migration of Jackrabbit 2.x repositories. But I'm not sure how easy it is
to imple
On 28.1.14 8:39 , Marcel Reutegger wrote:
Hi,
Failed tests:
addNodes[2](org.apache.jackrabbit.oak.jcr.ConcurrentAddIT):
javax.jcr.InvalidItemStateException: OakState0001: Unresolved conflicts
in /test/node4
This doesn't seem to be related to my changes. Anyone else seen such
before? Does the
On 28.1.14 8:39 , Marcel Reutegger wrote:
Hi,
Failed tests:
addNodes[2](org.apache.jackrabbit.oak.jcr.ConcurrentAddIT):
javax.jcr.InvalidItemStateException: OakState0001: Unresolved conflicts
in /test/node4
This doesn't seem to be related to my changes. Anyone else seen such
before? Does the
On 28.1.14 8:39 , Marcel Reutegger wrote:
Hi,
Failed tests:
addNodes[2](org.apache.jackrabbit.oak.jcr.ConcurrentAddIT):
javax.jcr.InvalidItemStateException: OakState0001: Unresolved conflicts
in /test/node4
This doesn't seem to be related to my changes. Anyone else seen such
before? Does the
Hi,
I have been working on enabling Jackrabbit data stores in OAK (tracked via
OAK-805, OAK-1157).
I need some clarification on how best to support the configuration needed
for these DataStores in OAK. How that is done in my current implementation
is to have separate configuration objects created
36 matches
Mail list logo