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 uniqueness enforcement which is somehow too eager (I'm thinking about restarts) or the fact that there is no proper cleanup of the DB data between the unit tests (or is there?). alex On Thu, Apr 4, 2013 at 5:30 PM, Alex Parvulescu <[email protected]>wrote: > 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 <[email protected]>wrote: > >> Hi, >> >> On Thu, Apr 4, 2013 at 6:14 PM, Alex Parvulescu >> <[email protected]> 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. I'm looking at it. >> >> BR, >> >> Jukka Zitting >> > >
