You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Uwe Schindler (JIRA)" <ji...@apache.org> on 2013/05/10 01:06:10 UTC
[jira] [Updated] (LUCENE-2338) Some tests catch Exceptions in
separate threads and just print a stack trace - the test does not fail
[ https://issues.apache.org/jira/browse/LUCENE-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uwe Schindler updated LUCENE-2338:
----------------------------------
Fix Version/s: (was: 4.3)
4.4
> Some tests catch Exceptions in separate threads and just print a stack trace - the test does not fail
> -----------------------------------------------------------------------------------------------------
>
> Key: LUCENE-2338
> URL: https://issues.apache.org/jira/browse/LUCENE-2338
> Project: Lucene - Core
> Issue Type: Test
> Components: general/build
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: 4.4
>
>
> Some tests catch Exceptions in separate threads and just print a stack trace - the test does not fail. The test should fail. Since LUCENE-2274, the LuceneTestCase(J4) class installs an UncaughtExceptionHandler, so this type of catching and solely printing a Stack trace is a bad idea. Problem is, that the run() method of threads is not allowed to throw checked Exceptions.
> Two possibilities:
> - Catch checked Exceptions in the run() method and wrap into RuntimeException or call Assert.fail() instead
> - Use Executors
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org