[
https://issues.apache.org/jira/browse/OAK-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592271#comment-13592271
]
Jukka Zitting commented on OAK-624:
-----------------------------------
I'm currently seeing the following TCK test failures (beyond the known issues):
{noformat}
testReferenceProperty(org.apache.jackrabbit.test.api.SetValueConstraintViolationExceptionTest):
setValue(Node value) must throw a ConstraintViolationException if the change
would violate a node type constraint either immediately or on save
testMultipleReferenceProperty(org.apache.jackrabbit.test.api.SetValueConstraintViolationExceptionTest):
setValue(Value[] values) must throw a ConstraintViolationException if the
change
would violate a node type constraint either immediately or on save
testReferenceProperty(org.apache.jackrabbit.test.api.SetPropertyConstraintViolationExceptionTest):
setProperty(String name, Node value) must throw a
ConstraintViolationException
if the change would violate a node type constraint either immediately or on
save
testResidualAndLegalType(org.apache.jackrabbit.test.api.nodetype.CanAddChildNodeCallWithNodeTypeTest):
NodeType.canAddChildNode(String childNodeName, String nodeTypeName) must
return
true for a not defined childNodeName if nodeTypeName matches the type of a
residual child node def
{noformat}
I wonder if these are really caused by the SegmentMK as such, or if there's
something like a built-in assumption about child node ordering in the node type
code.
> Run Oak-Jcr tests using the SegmentMK
> -------------------------------------
>
> Key: OAK-624
> URL: https://issues.apache.org/jira/browse/OAK-624
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: it
> Reporter: Alex Parvulescu
> Priority: Minor
> Attachments: t3-csv.log.zip
>
>
> It will take some time until the code stabilizes so I've created this issue
> to track potential transient issues with the oak-jcr tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
