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/657
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
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/656
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source S
On 7.10.14 10:30 , Tommaso Teofili wrote:
2014-10-07 18:15 GMT+02:00 Rob Ryan :
I'm not so sure about the conclusion that because the events of interest
are local you can safely use userData. IIUC under heavy load local events
may be aggregated to mitigate the load and in that process 'localn
2014-10-07 18:15 GMT+02:00 Rob Ryan :
> I'm not so sure about the conclusion that because the events of interest
> are local you can safely use userData. IIUC under heavy load local events
> may be aggregated to mitigate the load and in that process 'localness' is
> lost...
>
maybe I missed that
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/606
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-vm_ubuntu
Build Reason: scheduler
Build Source Stamp:
hi michael
should be fixed now... if i overlooked something i should have
let it rest until tomorrow ;-)
good night
angela
On 07/10/14 18:59, "Angela Schreiber" wrote:
>ok... that looks like my fault ;-)
>i will look into it tomorrow
>
>angela
>
>On 07/10/14 18:08, "Michael Dürig" wrote:
>
>>
ok... that looks like my fault ;-)
i will look into it tomorrow
angela
On 07/10/14 18:08, "Michael Dürig" wrote:
>
>I now see org.apache.jackrabbit.oak.jcr.tck.SecurityIT failing. This
>seems to have started with http://svn.apache.org/r1629876.
>
>Michael
>
>On 7.10.14 3:47 , Michael Dürig wrot
I'm not so sure about the conclusion that because the events of interest are
local you can safely use userData. IIUC under heavy load local events may be
aggregated to mitigate the load and in that process 'localness' is lost...
Can anyone more knowledgeable address that point?
Thanks,
-Rob
--
I now see org.apache.jackrabbit.oak.jcr.tck.SecurityIT failing. This
seems to have started with http://svn.apache.org/r1629876.
Michael
On 7.10.14 3:47 , Michael Dürig wrote:
This is tracked via https://issues.apache.org/jira/browse/OAK-2165.
Unfortunately the failure only occurs on this ins
On 2014-10-07 15:47, Michael Dürig wrote:
This is tracked via https://issues.apache.org/jira/browse/OAK-2165.
Unfortunately the failure only occurs on this instance. I'm trying to
track it down.
...
FWIW, this is one of those tests that occasionally fail on Windows.
Best regards, Julian
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/602
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-vm_ubuntu
Build Reason: scheduler
Build Source Stamp: [b
ok... thanks for the pointer!
angela
On 07/10/14 15:47, "Michael Dürig" wrote:
>This is tracked via https://issues.apache.org/jira/browse/OAK-2165.
>Unfortunately the failure only occurs on this instance. I'm trying to
>track it down.
>
>On 7 October 2014 15:42, Angela Schreiber wrote:
>> the f
This is tracked via https://issues.apache.org/jira/browse/OAK-2165.
Unfortunately the failure only occurs on this instance. I'm trying to
track it down.
On 7 October 2014 15:42, Angela Schreiber wrote:
> the failing tests are:
>
> -
> testRenameEventHandling(org.apache.jackrabbit.oak.jcr.Jackrabb
the failing tests are:
-
testRenameEventHandling(org.apache.jackrabbit.oak.jcr.JackrabbitNodeTest):
Expected NODE_MOVED event upon renaming a node (received: latch1 timed out
none; next event after additional addNode/save operation: type 2
1412666439717ms /testroot/a, type 32 1412666439717ms /tes
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/651
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
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/650
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source S
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/647
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source Stam
Thanks a lot, it is working much better now.
-Original Message-
From: Marcel Reutegger [mailto:mreut...@adobe.com]
Sent: mardi 7 octobre 2014 10:59
To: oak-dev@jackrabbit.apache.org
Subject: Re: OakMerge0001: Failed to merge changes to the underlying store
Hi,
you forgot to shut down t
Hi Michael,
thanks for the information, despite the given limitations I think it could
still work for my use case, as the distinction I need to make by means of
userData should always be on local events.
Regards,
Tommaso
2014-10-03 17:10 GMT+02:00 Michael Dürig :
>
> Hi Tommaso,
>
> Unfortunat
Hi,
you forgot to shut down the DocumentNodeStore. You need to add
this do your finally clause:
if (nodeStore != null) {
nodeStore.dispose();
}
It isn't intuitive why this leads to this exception, but let me
try to explain.
The DocumentNodeStore allows deployments with multiple instances
w
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/598
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-vm_ubuntu
Build Reason: scheduler
Build Source Stamp:
21 matches
Mail list logo