Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Wed, 30 Jan 2013 12:03:16 +0000 (UTC)
From: "Bart van der Schans (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12629865.1359540424135.214869.1359547396246@arcas>
In-Reply-To: <JIRA.12629865.1359540424135@arcas>
References: <JIRA.12629865.1359540424135@arcas>
Subject: [jira] [Commented] (JCR-3504) ConcurrentImportTest failure
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bart van der Schans commented on JCR-3504:
------------------------------------------

Hi Jukka,

The test succeeds for me. Do you have some pointers about what goes wrong and in which environment?

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