DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.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://nagoya.apache.org/bugzilla/show_bug.cgi?id=12817 capture of stdout/stderr in JUnit task causes out of memory exception Summary: capture of stdout/stderr in JUnit task causes out of memory exception Product: Ant Version: 1.5 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In JUnitTestRunner.java, capturing stdout and stderr to a ByteArrayOutputStream causes out of memory exceptions to occur when test cases use classes that print large volumes of text to either output stream (*cough* *cocobase*). In some cases, this console output cannot be turned off without decompiling a third party jar. Capturing this output occurs regardless of whether or not printsummary is on, off, or withStdAndErr. The printsummary attribute should be passed into the JUnitTestRunner class and tested to check if it is equal to withStdAndErr and, if not, don't capture the output and error streams. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
