You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2015/04/16 17:11:59 UTC
[jira] [Comment Edited] (OAK-2751) Test failures with
EnableConcurrentAddRemove feature enabled on 1.0 branch
[ https://issues.apache.org/jira/browse/OAK-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498051#comment-14498051 ]
Marcel Reutegger edited comment on OAK-2751 at 4/16/15 3:11 PM:
----------------------------------------------------------------
This issue only occurs with the DocumentMK, which is also the reason why it doesn't happen on the 1.2 branch. In the 1.2 branch the RandomizedTest doesn't use the DocumentMK, but rather a NodeStoreKernel on top of the DocumentNodeStore.
The DocumentMK.commit() method does not check if a node exists for a property patch. I created a separate issue to fix this: OAK-2780.
was (Author: mreutegg):
This issue only occurs with the DocumentMK, which is also the reason why it doesn't happen on the 1.2 branch. In the 1.2 branch the RandomizedTest does use the DocumentMK, but rather a NodeStoreKernel on top of the DocumentNodeStore.
The DocumentMK.commit() method does not check if a node exists for a property patch. I created a separate issue to fix this: OAK-2780.
> Test failures with EnableConcurrentAddRemove feature enabled on 1.0 branch
> --------------------------------------------------------------------------
>
> Key: OAK-2751
> URL: https://issues.apache.org/jira/browse/OAK-2751
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Chetan Mehrotra
> Assignee: Marcel Reutegger
> Priority: Blocker
> Fix For: 1.0.13
>
> Attachments: OAK-2751-set-prop-on-delete-should-conflict.patch
>
>
> With merge of OAK-2673 some failures were seen in oak-it/mk which are not seen on trunk. This require further change in patch to shutdown the feature completely.
> We still need to investigate why this happened and ensure that test pass with this feature enabled
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)