You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2010/12/09 12:41:02 UTC

[jira] Created: (LUCENE-2807) Improve test debuggability through ant

Improve test debuggability through ant
--------------------------------------

                 Key: LUCENE-2807
                 URL: https://issues.apache.org/jira/browse/LUCENE-2807
             Project: Lucene - Java
          Issue Type: Improvement
          Components: Tests
            Reporter: Michael McCandless
             Fix For: 4.0


Some small improvements would go a long ways...

When trying to debug an intermittent fail, I usually run w/ -Dtests.verbose=true and w/ many iters.  But because the formatter buffers this can hit OOME, so maybe we make an unbuffered formatter.  Also, it'd be nice if we could have the formatter discard output for a given iter if there was no failure, and I think the iters should stop as soon as a failure is hit.

Maybe somehow we make a new tests.mode that would switch on these behaviours?

Unbuffered formatter is also vital when debugging a deadlock...

-- 
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] Commented: (LUCENE-2807) Improve test debuggability through ant

Posted by "Michael McCandless (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969757#action_12969757 ] 

Michael McCandless commented on LUCENE-2807:
--------------------------------------------

bq. if you are using multiple iterations, we use the multiple iterations formatter, etc?

Sounds great!

> Improve test debuggability through ant
> --------------------------------------
>
>                 Key: LUCENE-2807
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2807
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Tests
>            Reporter: Michael McCandless
>             Fix For: 4.0
>
>
> Some small improvements would go a long ways...
> When trying to debug an intermittent fail, I usually run w/ -Dtests.verbose=true and w/ many iters.  But because the formatter buffers this can hit OOME, so maybe we make an unbuffered formatter.  Also, it'd be nice if we could have the formatter discard output for a given iter if there was no failure, and I think the iters should stop as soon as a failure is hit.
> Maybe somehow we make a new tests.mode that would switch on these behaviours?
> Unbuffered formatter is also vital when debugging a deadlock...

-- 
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] Commented: (LUCENE-2807) Improve test debuggability through ant

Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969703#action_12969703 ] 

Robert Muir commented on LUCENE-2807:
-------------------------------------

Or we could just default to the right one based on what options you use?

if you are using multiple iterations, we use the multiple iterations formatter, etc?

> Improve test debuggability through ant
> --------------------------------------
>
>                 Key: LUCENE-2807
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2807
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Tests
>            Reporter: Michael McCandless
>             Fix For: 4.0
>
>
> Some small improvements would go a long ways...
> When trying to debug an intermittent fail, I usually run w/ -Dtests.verbose=true and w/ many iters.  But because the formatter buffers this can hit OOME, so maybe we make an unbuffered formatter.  Also, it'd be nice if we could have the formatter discard output for a given iter if there was no failure, and I think the iters should stop as soon as a failure is hit.
> Maybe somehow we make a new tests.mode that would switch on these behaviours?
> Unbuffered formatter is also vital when debugging a deadlock...

-- 
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Resolved] (LUCENE-2807) Improve test debuggability through ant

Posted by "Michael McCandless (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael McCandless resolved LUCENE-2807.
----------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 4.1)
                   4.0

Dawid already fixed these issues (thanks!).
                
> Improve test debuggability through ant
> --------------------------------------
>
>                 Key: LUCENE-2807
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2807
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: general/test
>            Reporter: Michael McCandless
>             Fix For: 4.0
>
>
> Some small improvements would go a long ways...
> When trying to debug an intermittent fail, I usually run w/ -Dtests.verbose=true and w/ many iters.  But because the formatter buffers this can hit OOME, so maybe we make an unbuffered formatter.  Also, it'd be nice if we could have the formatter discard output for a given iter if there was no failure, and I think the iters should stop as soon as a failure is hit.
> Maybe somehow we make a new tests.mode that would switch on these behaviours?
> Unbuffered formatter is also vital when debugging a deadlock...

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