Re: [Errored] apache/jackrabbit-oak#1119 (trunk - 503451c)

2013-04-04 Thread Alex Parvulescu
this is really bugging me. is anybody else seeing the same problems? I don't have any errors on my build: svn co https://svn.apache.org/repos/asf/jackrabbit/oak/trunk oak-testbuild cd oak-testbuild mvn clean install -PintegrationTesting . [INFO] BUILD SUCCESS [INFO]

Re: [Errored] apache/jackrabbit-oak#1119 (trunk - 503451c)

2013-04-04 Thread Jukka Zitting
Hi, On Thu, Apr 4, 2013 at 6:14 PM, Alex Parvulescu alex.parvule...@gmail.com wrote: this is really bugging me. is anybody else seeing the same problems? I don't have any errors on my build: You probably don't have MongoDB running locally; the errors come from the MongoMK/SegmentMK TCK runs.

Re: [Errored] apache/jackrabbit-oak#1119 (trunk - 503451c)

2013-04-04 Thread Alex Parvulescu
ouch, you are right. I'm going to try out a mongo build then. thanks, alex On Thu, Apr 4, 2013 at 5:22 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi, On Thu, Apr 4, 2013 at 6:14 PM, Alex Parvulescu alex.parvule...@gmail.com wrote: this is really bugging me. is anybody else seeing

Re: [Errored] apache/jackrabbit-oak#1119 (trunk - 503451c)

2013-04-04 Thread Alex Parvulescu
right, it would appear that OAK-748 introduced this problem, but it's not that easy to take it all out. it seems the errors come from trying to reindex the initial content and throwing an error because the index content is already there (unique uuid ftw). It's either the fact that we have

Re: [Errored] apache/jackrabbit-oak#1119 (trunk - 503451c)

2013-04-04 Thread Jukka Zitting
Hi, On Thu, Apr 4, 2013 at 8:08 PM, Alex Parvulescu alex.parvule...@gmail.com wrote: right, it would appear that OAK-748 introduced this problem, but it's not that easy to take it all out. Yep, that looks like the case. It's also possible that my changes to OAK-709 are contributing to the

Re: [Errored] apache/jackrabbit-oak#1119 (trunk - 503451c)

2013-04-04 Thread Jukka Zitting
Hi, On Thu, Apr 4, 2013 at 8:31 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: On Thu, Apr 4, 2013 at 8:08 PM, Alex Parvulescu alex.parvule...@gmail.com wrote: right, it would appear that OAK-748 introduced this problem, but it's not that easy to take it all out. Yep, that looks like the