jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-802) Occasional type validation errors in TCK setup
Date Wed, 01 May 2013 08:10:16 GMT

    [ https://issues.apache.org/jira/browse/OAK-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646449#comment-13646449

Jukka Zitting commented on OAK-802:

Improved error reporting in http://svn.apache.org/r1477927
> Occasional type validation errors in TCK setup
> ----------------------------------------------
>                 Key: OAK-802
>                 URL: https://issues.apache.org/jira/browse/OAK-802
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, jcr
>         Environment: happens at least on my laptop and on an ec2 m1.xlarge instance
>            Reporter: Jukka Zitting
> Occasionally, like in 1% of the cases, I see a default {{mvn clean install -PintegrationTesting}}
build fail with lots of type validation errors from the TCK. A typical example is:
> {noformat}
> testScoreColumn(org.apache.jackrabbit.test.api.query.SQLQueryLevel2Test)  Time elapsed:
0.01 sec  <<< ERROR!
> javax.jcr.nodetype.ConstraintViolationException: org.apache.jackrabbit.oak.api.CommitFailedException:
OakConstraint0001: /testroot/node1: Incorrect node type of child node node1 [nt:unstructured]
> 	at org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.newRepositoryException(SessionDelegate.java:331)
> 	at org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.save(SessionDelegate.java:196)
> 	at org.apache.jackrabbit.oak.jcr.SessionImpl.save(SessionImpl.java:369)
> 	at org.apache.jackrabbit.test.api.query.AbstractQueryLevel2Test.setUpFullTextTest(AbstractQueryLevel2Test.java:45)
> 	at org.apache.jackrabbit.test.api.query.SQLQueryLevel2Test.testScoreColumn(SQLQueryLevel2Test.java:41)
> {noformat}
> See https://www.dropbox.com/s/57cps6ys0etd9an/org.apache.jackrabbit.oak.jcr.tck.QueryIT.txt
for the failsafe output of such an case.
> I've been able to reproduce the problem with a build loop like the following on my laptop
and on a m1.xlarge ec2 instance (it didn't show up on a m1.medium instance):
> {code:none}
> for i in `seq 1 100`; do
>     mvn clean install -PintegrationTesting > build$i.log 2>&1
> done
> {code}

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

View raw message