[
https://issues.apache.org/jira/browse/SUREFIRE-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645275#comment-17645275
]
Elliotte Rusty Harold commented on SUREFIRE-2103:
-------------------------------------------------
Thanks. This sounds like a bug we should fix.
That said, it is very bad practice for any test, integration or unit, to write
1 GB of logs. In fact it's bad practice for a test to write 1 MB of logs. Tests
should log detailed failure information for any test that fails, and absolutely
nothing for any test that passes. Otherwise the information you need to debug a
failing test is lost in a sea of log junk no one cares about and no one will
ever read.
Irrespective of whether we fix this bug, I strongly recommend fixing the tests
to log far, far less data.
> <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: Blocker
>
> 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)
