[MNG-7130] Integration with Jansi and windows console create JVM fork errors with lots of output during tests

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Incomplete
• Affects Version/s: 3.6.3
• Component/s: Core
• Assignee: Unassigned
• Reporter: Philippe Deslauriers
• Created: 25/Mar/21 14:37
• Updated: 19/Sep/21 08:51
• Resolved: 19/Sep/21 08:51

Description

see my answer to this thread

https://stackoverflow.com/a/66801171/1634131

 

Build with lots of console ouput (15Mb+ in my case) in surefire / failsafe tests fails with this error :

 

The forked VM terminated without saying properly goodbye. VM crash or System.exit called

 

This happens even with -B  (batch) option.

 

On a given project this would fails systematically in a new windows console (cmd.exe)

[path_to_jdk]\java.exe -Dmaven.home=[path_to_maven]\apache-maven-3.6.3 -Dclassworlds.conf=[path_to_maven]\bin..\bin\m2.conf -Dmaven.multiModuleProjectDirectory=[path_to_myproject] -Dfile.encoding=UTF-8  -classpath [path_to_maven]\boot\plexus-classworlds-2.6.0.jar org.codehaus.plexus.classworlds.launcher.Launcher clean install -B

This will always works in a new console window (cmd.exe).

[path_to_jdk]\java.exe -Dmaven.home=[path_to_maven]\apache-maven-3.6.3 -Dclassworlds.conf=[path_to_maven]\bin..\bin\m2.conf -Dmaven.multiModuleProjectDirectory=[path_to_myproject] -Dfile.encoding=UTF-8 -Djansi.force=true -Djansi.passthrough=true -classpath [path_to_maven]\boot\plexus-classworlds-2.6.0.jar org.codehaus.plexus.classworlds.launcher.Launcher clean install -B

Notice that both command have -B (batch mode which should turn off coloring), and the only difference is

 

-Djansi.force=true -Djansi.passthrough=true

 

maven-surefire-plugin/useSystemClassLoader does not have an impact on test results