[
https://issues.apache.org/jira/browse/OAK-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592295#comment-13592295
]
Alex Parvulescu edited comment on OAK-624 at 3/4/13 3:51 PM:
-------------------------------------------------------------
wacky type selection on the test again: #testResidualAndLegalType apparently
chooses _nt:hierarchyNode_ as a type for the child node of a _nt:folder_ node,
but because that is abstract it cannot be used, so NodeTypeImpl#canAddChildNode
returns false right away.
> or if there's something like a built-in assumption about child node ordering
> in the node type code.
I think the node type selection mechanism isn't too smart, it can choose the
first node type it finds (which is in fact influenced by the SegmentMK) and it
can be a bad selection that makes the test fail.
see for example JCR-3524 for a similar issue
was (Author: alex.parvulescu):
wacky type selection on the test again: #testResidualAndLegalType
apparently chooses _nt:hierarchyNode_ as a type for the child node, but because
that is abstract it cannot be used, so NodeTypeImpl#canAddChildNode returns
false right away.
> 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
