lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-4879) Filter stack traces on console output.
Date Tue, 26 Mar 2013 02:33:15 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613415#comment-13613415
] 

Robert Muir commented on LUCENE-4879:
-------------------------------------

Thank you very much for this! This is a huge improvement, stacktraces for a simple test failure
are like 3 lines long instead of 45 now and can be seen without scrolling (with room for even
a few debugging prints too!)
                
> Filter stack traces on console output.
> --------------------------------------
>
>                 Key: LUCENE-4879
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4879
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: general/test
>            Reporter: Dawid Weiss
>            Assignee: Dawid Weiss
>            Priority: Minor
>             Fix For: 5.0, 4.3
>
>
> We could filter stack traces similar to what ANT's JUnit task does. It'd remove some
of the noise and make them shorter. I don't think the lack of stack filtering is particularly
annoying and it's always to have an explicit view of what and where happened but since Robert
requested this I'll add it.
> We can always make it a (yet another) test.* option :)

--
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


Mime
View raw message