[ https://issues.apache.org/jira/browse/SUREFIRE-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tibor Digana closed SUREFIRE-1333. ---------------------------------- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commitdiff;h=179abbf026902e44b1d95f7ef41b69bdb24434df > Process pending events from forked process after exited and then finish > forked Thread. > -------------------------------------------------------------------------------------- > > Key: SUREFIRE-1333 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1333 > Project: Maven Surefire > Issue Type: Bug > Components: process forking > Reporter: Tibor Digana > Assignee: Tibor Digana > Fix For: 2.19.2 > > > It is a fix after Jenkins build failure: > https://builds.apache.org/job/maven-surefire/org.apache.maven.surefire$surefire-integration-tests/1673/testReport/junit/org.apache.maven.surefire.its/ConsoleOutputIT/largerSoutThanMemory/ > The events go to Queue from std/out of forked JVM. The events are processed > asynchronously. Processing of them should prolong #close() method in > ThreadedStreamConsumer. Max 5 minutes timeout. > This should prevent from particular exit when heavily a lot of console logs > is printed by forked Test set. > [ERROR] Process Exit Code: 0 > [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? -- This message was sent by Atlassian JIRA (v6.3.15#6346)