ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 12817] - capture of stdout/stderr in JUnit task causes out of memory exception
Date Sun, 26 Feb 2006 22:47:07 GMT
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=12817>.
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=12817





------- Additional Comments From mgrosso@acm.org  2006-02-26 23:47 -------
Created an attachment (id=17800)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=17800&action=view)
patch for bug 12817 to leave stdout and err alone if showoutput is true.

I'm attaching another proposed patch. This one uses the existing showoutput
parameter and, if that variable is true, stderr and stdout are left alone,
unmolested, and no attempt is made to capture either stream in a byte array.
Stefan's comments that this bug cant be fixed confused me, since none of the
other JUnit formatters are attempting to buffer the entire stream afaik, and
this patch did fix the problem for me.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message