https://bz.apache.org/bugzilla/show_bug.cgi?id=63436
--- Comment #3 from Jaikiran Pai <jaiki...@apache.org> --- Thank you for reporting this and the patch. However, the reason it's been coded that way was to avoid loading the entire system.out/system.err messages into memory and potentially running into OOM. This was the motivation to have (although a bit involved logic) it stream instead of holding the whole content in memory and then writing it into that report. This isn't a theoretical case either since issues like these OOMs have been reported in our JUnit task of Ant. Having said that, the XML is expected to be well formed as well as usable by the junitreport. Can you please attach a sample xml which got generated and which is causing issues with the junitreport task? -- You are receiving this mail because: You are the assignee for the bug.
