Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Message-ID: <137928859.393821269187407124.JavaMail.jira@brutus.apache.org>
Date: Sun, 21 Mar 2010 16:03:27 +0000 (UTC)
From: "Uwe Schindler (JIRA)" <jira@apache.org>
To: java-dev@lucene.apache.org
Subject: [jira] Assigned: (LUCENE-1814) Some Lucene tests try and use a
 Junit Assert in new threads
In-Reply-To: <813597523.1250372954842.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/LUCENE-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Uwe Schindler reassigned LUCENE-1814:
-------------------------------------

    Assignee: Uwe Schindler

> Some Lucene tests try and use a Junit Assert in new threads
> -----------------------------------------------------------
>
>                 Key: LUCENE-1814
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1814
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Assignee: Uwe Schindler
>            Priority: Minor
>
> There are a few cases in Lucene tests where JUnit Asserts are used inside a new threads run method - this won't work because Junit throws an exception when a call to Assert fails - that will kill the thread, but the exception will not propagate to JUnit - so unless a failure is caused later from the thread termination, the Asserts are invalid.
> TestThreadSafe
> TestStressIndexing2
> TestStringIntern

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org