https://bz.apache.org/bugzilla/show_bug.cgi?id=63436
--- Comment #4 from mse...@guh-software.de --- (In reply to Jaikiran Pai from comment #3) > 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're right, XML "Files" inside sysout/err are escaped correct in junitreport task. Maybe my problems came all from https://bz.apache.org/bugzilla/show_bug.cgi?id=63446 Anyway, even JUnit 5's org.junit.platform.reporting.legacy.xml.LegacyXmlReportGeneratingListener is using CDATA for sysout/err. And they do it in a way without having sysout/err in memory. Please see: https://github.com/junit-team/junit5/blob/master/junit-platform-reporting/src/main/java/org/junit/platform/reporting/legacy/xml/XmlReportWriter.java -- You are receiving this mail because: You are the assignee for the bug.
