Re: Exceptions in TestConcurrentMergeScheduler

"Chris Hostetter" <[EMAIL PROTECTED]> wrote: > > : But it'd be nice to do this across the board, ie, for any junit test > : if one of CMS's threads (or, threads launched elsewhere) hits an > : unhandled exception, fail the testcase that's currently running. > : I'll dig and see if there's some ce

Re: Exceptions in TestConcurrentMergeScheduler

OK, I think I found one possibility here. With ant's junit task, you can define a custom formatter implementing this interface: org.apache.tools.ant.taskdefs.optional.junit.JUnitResultFormatter That interface has a method endTestSuite that is invoked once at the end of all the test cases. So

Re: Exceptions in TestConcurrentMergeScheduler

Mike, Would it work to have a common LuceneTestCase base class that could do that check and fail() in tearDown? Erik On Oct 4, 2007, at 5:31 AM, Michael McCandless wrote: OK, I think I found one possibility here. With ant's junit task, you can define a custom formatter implement

Re: Exceptions in TestConcurrentMergeScheduler

Indeed this will work! I was unsure whether you could fail() a test inside tearDown() but it seems to work fine -- I just tested it. Only downside is a mass replacement of all "extends TestCase" with "extends LuceneTestCase" (but that's a one time cost, now), and making sure tearDown() always ca

[jira] Created: (LUCENE-1018) intermittant exceptions in TestConcurrentMergeScheduler

intermittant exceptions in TestConcurrentMergeScheduler --- Key: LUCENE-1018 URL: https://issues.apache.org/jira/browse/LUCENE-1018 Project: Lucene - Java Issue Type: Bug Componen

[jira] Updated: (LUCENE-1018) intermittant exceptions in TestConcurrentMergeScheduler

[ https://issues.apache.org/jira/browse/LUCENE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-1018: --- Attachment: LUCENE-1018.patch Attached patch, fixing the scoping issue Ning found an

[jira] Updated: (LUCENE-1017) BoostingTermQuery performance

[ https://issues.apache.org/jira/browse/LUCENE-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Keegan updated LUCENE-1017: - Attachment: BoostingTermQuery.patch Here is new version that traverses the term positions proper

[jira] Created: (LUCENE-1019) CustomScoreQuery should support multiple ValueSourceQueries

CustomScoreQuery should support multiple ValueSourceQueries --- Key: LUCENE-1019 URL: https://issues.apache.org/jira/browse/LUCENE-1019 Project: Lucene - Java Issue Type: Improvement

[jira] Issue Comment Edited: (LUCENE-1019) CustomScoreQuery should support multiple ValueSourceQueries

[ https://issues.apache.org/jira/browse/LUCENE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532557 ] fizx edited comment on LUCENE-1019 at 10/4/07 6:08 PM: --- Here's the patch! BTW, I'll e

[jira] Updated: (LUCENE-1019) CustomScoreQuery should support multiple ValueSourceQueries

[ https://issues.apache.org/jira/browse/LUCENE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyle Maxwell updated LUCENE-1019: - Attachment: CustomMultiQuery.v0.diff Here's the patch! > CustomScoreQuery should support multip

[jira] Commented: (LUCENE-1019) CustomScoreQuery should support multiple ValueSourceQueries

[ https://issues.apache.org/jira/browse/LUCENE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532560 ] Hoss Man commented on LUCENE-1019: -- this class seems to assume that the ValueSourceQueries should be multipled ...

Re: svn commit: r582054: typo

Hoss, Thanks for that. There is a typo, it says "llthough" in one of the javadocs. Regards, Paul Elschot - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]