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=30879>. 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=30879 OutOfMemoryException at JUnitTestRunner.java:342 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Enhancement ------- Additional Comments From [EMAIL PROTECTED] 2004-08-31 15:40 ------- Out of curiosity why don't you configure your logger to log somewhere else than the console ? Especially for a stress test. The output capture is absolutely not designed to handle huge amount of data. This data is dispatched to every formatter once the test is finished (along with result, timing, etc...), so the easiest solution was just to keep everything in memory. It could be eventually redesigned so that it outputs all the data to a temporary file which input stream is then created and set for every formatter (at least this is what I'm thinking about) but this won't improve things much except complicate things. I'm downgrading the severity from major to enhancement for now. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
