jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3504) ConcurrentImportTest failure
Date Wed, 30 Jan 2013 12:29:12 GMT

    [ https://issues.apache.org/jira/browse/JCR-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566417#comment-13566417
] 

Jukka Zitting commented on JCR-3504:
------------------------------------

See https://builds.apache.org/job/Jackrabbit-trunk/2048/ for an example. The test also fails
on my Windows laptop.

As a concurrency test, ConcurrentImportTest is by definition somewhat non-deterministic so
it's not a surprise that it doesn't fail always or in all environments.
                
> ConcurrentImportTest failure
> ----------------------------
>
>                 Key: JCR-3504
>                 URL: https://issues.apache.org/jira/browse/JCR-3504
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.6
>            Reporter: Jukka Zitting
>
> After JCR-3277 it seems like the consistency checker can uncover new problems that the
ConcurrentImportTest couldn't detect earlier. Instead of reverting JCR-3277 it makes more
sense to investigate and fix this newly detected problem. Until we're there, ConcurrentImportTest
should be marked as a known issue.

--
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

Mime
View raw message