You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Travis-CI <no...@travis-ci.org> on 2012/12/20 00:48:55 UTC
[Broken] apache/jackrabbit-oak#322 (trunk - c0e2852)
Build Update for apache/jackrabbit-oak
-------------------------------------
Build: #322
Status: Broken
Duration: 35 minutes and 11 seconds
Commit: c0e2852 (trunk)
Author: Michael Duerig
Message: OAK-531: NodeBuilder deleted child nodes can come back
No need to traverse the parent hierarchy. Just correctly check whether a node has been removed from the parent builder by checking whether it is present in the base state but not present in the write state.
git-svn-id: https://svn.apache.org/repos/asf/jackrabbit/oak/trunk@1424213 13f79535-47bb-0310-9956-ffa450edef68
View the changeset: https://github.com/apache/jackrabbit-oak/compare/ec961a382325...c0e2852399cc
View the full build log and details: https://travis-ci.org/apache/jackrabbit-oak/builds/3748730
--
You can configure recipients for build notifications in your .travis.yml file. See http://bit.ly/lCybCJ
The delivery of this notification was kindly sponsored by Postmark. Send transactional email confidently using http://postmarkapp.com
Re: [Broken] apache/jackrabbit-oak#322 (trunk - c0e2852)
Posted by Alex Parvulescu <al...@gmail.com>.
hi,
I switched the code to use the SerialMergeScheduler in rev 1430280 to fix
the error for now as a temp solution.
best,
alex
On Thu, Dec 20, 2012 at 9:22 AM, Jukka Zitting <ju...@gmail.com>wrote:
> Hi,
>
> On Thu, Dec 20, 2012 at 10:13 AM, Michael Dürig <md...@apache.org>
> wrote:
> > I see these from time to time on my local machine also. Any idea what
> could
> > cause this?
>
> We should probably switch the Lucene index to use SerialMergeScheduler
> instead of the default one that starts background threads for merging.
>
> Alternatively, as discussed separately, we may need to switch the
> Lucene indexer from a CommitHook to an Observer (with some cluster
> synchronization mechanism) so it can better run things in background.
>
> BR,
>
> Jukka Zitting
>
Re: [Broken] apache/jackrabbit-oak#322 (trunk - c0e2852)
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Thu, Dec 20, 2012 at 10:13 AM, Michael Dürig <md...@apache.org> wrote:
> I see these from time to time on my local machine also. Any idea what could
> cause this?
We should probably switch the Lucene index to use SerialMergeScheduler
instead of the default one that starts background threads for merging.
Alternatively, as discussed separately, we may need to switch the
Lucene indexer from a CommitHook to an Observer (with some cluster
synchronization mechanism) so it can better run things in background.
BR,
Jukka Zitting
Re: [Broken] apache/jackrabbit-oak#322 (trunk - c0e2852)
Posted by Michael Dürig <md...@apache.org>.
I see these from time to time on my local machine also. Any idea what
could cause this?
Michael
Running org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexQueryTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 1.319 sec
Running org.apache.jackrabbit.oak.jcr.query.QueryJcrTest
Exception in thread "Lucene Merge Thread #1"
org.apache.lucene.index.MergePolicy$MergeException:
java.lang.AssertionError:
info.dir=org.apache.jackrabbit.oak.plugins.index.lucene.ReadWriteOakDirectory@2110fc
lockFactory=org.apache.lucene.store.NoLockFactory@12a0f6c vs
org.apache.jackrabbit.oak.plugins.index.lucene.ReadWriteOakDirectory@e222eb
lockFactory=org.apache.lucene.store.NoLockFactory@12a0f6c
at
org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:535)
at
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:508)
Caused by: java.lang.AssertionError:
info.dir=org.apache.jackrabbit.oak.plugins.index.lucene.ReadWriteOakDirectory@2110fc
lockFactory=org.apache.lucene.store.NoLockFactory@12a0f6c vs
org.apache.jackrabbit.oak.plugins.index.lucene.ReadWriteOakDirectory@e222eb
lockFactory=org.apache.lucene.store.NoLockFactory@12a0f6c
at
org.apache.lucene.index.IndexWriter$ReaderPool.get(IndexWriter.java:503)
at
org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3678)
at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3354)
at
org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:402)
at
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:479)
On 19.12.12 23:48, Travis-CI wrote:
> Build Update for apache/jackrabbit-oak
> -------------------------------------
>
> Build: #322
> Status: Broken
>
> Duration: 35 minutes and 11 seconds
> Commit: c0e2852 (trunk)
> Author: Michael Duerig
> Message: OAK-531: NodeBuilder deleted child nodes can come back
> No need to traverse the parent hierarchy. Just correctly check whether a node has been removed from the parent builder by checking whether it is present in the base state but not present in the write state.
>
> git-svn-id: https://svn.apache.org/repos/asf/jackrabbit/oak/trunk@1424213 13f79535-47bb-0310-9956-ffa450edef68
>
> View the changeset: https://github.com/apache/jackrabbit-oak/compare/ec961a382325...c0e2852399cc
>
> View the full build log and details: https://travis-ci.org/apache/jackrabbit-oak/builds/3748730
>
> --
>
> You can configure recipients for build notifications in your .travis.yml file. See http://bit.ly/lCybCJ
>
> The delivery of this notification was kindly sponsored by Postmark. Send transactional email confidently using http://postmarkapp.com
>
>
>
>