You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2004/10/29 15:56:20 UTC
DO NOT REPLY [Bug 31962] -
Junit task -- display suite first
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31962>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31962
Junit task -- display suite first
------- Additional Comments From ddevienne@lgc.com 2004-10-29 13:56 -------
I concur. I'd like to see the test case name before too.
My reason is that we have lots of JNI/C++ code behind our Java code, and when
that code blows the VM away, we always have to guess which test case is the
likely culprit. The VM crash output does not always contain the Java stack
trace to figure this out.
And in any case, I agree with Howard that for long tests (which we also have),
it's better to see that something's running, and what. --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org