[ https://issues.apache.org/jira/browse/SUREFIRE-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliotte Rusty Harold resolved SUREFIRE-2103. --------------------------------------------- Resolution: Fixed sounds like it's fixed, comment and I'll reopen if it can still be reproduced > <system-err> and <system-info> causing Java heap space issue. > ------------------------------------------------------------- > > Key: SUREFIRE-2103 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2103 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin > Affects Versions: 3.0.0-M5, 3.0.0-M6 > Reporter: parita jivani > Priority: Critical > Fix For: waiting-for-feedback > > > We have Java test projects, which has different integration and UI tests. We > are upgrading failsafe and surefire version from 2.17 to 3.0.0-M5. After > upgrade few projects were failing with Java heap space. After analysing the > issue, we got to know that failsafe reports creation is causing the memory > issue. Failsafe plugin is writing <system-err> and <system-info> elements > with log details. In our case, build logs contains huge data of script > execution logs(around >= 1GB). While creating failsafe report, failsafe > plugin is writing entire logs to *.xml report and causing failure due to java > heap space. > > For issue resolution my suggestion is to get some configuration to > unable/disable option for <system-err> tags would really help. -- This message was sent by Atlassian Jira (v8.20.10#820010)