[
https://issues.apache.org/jira/browse/LUCENE-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847932#action_12847932
]
Uwe Schindler commented on LUCENE-1814:
---------------------------------------
This is fixed!
But some of the threads use a "own" exception handler calling
ex.printStackTrace(), and so those bugs are not detected. But all asserts in
foreign threads are fine now!
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
