[ https://issues.apache.org/jira/browse/LUCENE-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-2338.
----------------------------------------
Resolution: Fixed
Fix Version/s: 4.0
3.6
Our test framework fails tests w/ errant exceptions from threads now...
> 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 - Java
> Issue Type: Test
> Components: general/build
> Reporter: Uwe Schindler
> Fix For: 3.6, 4.0
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
|