blocks|key|1724446|text|Surefire+FAQ的这一部分可以帮助您：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1724447|1724448|+Surefire会失败，并显示消息"The+forked+VM+terminated+with+“。|blockquote|style|BOLD|1724449|1724450|Surefire在任何时候都不支持调用System.exit()的测试或任何被引用的库。如果他们这样做了，他们是不兼容的，你可能应该向库/供应商提交一个问题。或者，派生的VM也可能因为许多原因而崩溃，这也可能导致此问题的发生。查找指示VM崩溃的经典"hs_err*“文件，或者在测试执行时检查运行maven的日志输出。崩溃进程的一些“异常”输出可能会被转储到控制台/日志中。如果这种情况发生在CI环境中，并且仅在一段时间后运行，那么您的测试套件很可能会泄漏某种操作系统级别的资源，这会使情况在每次运行时变得更糟。常规的操作系统级别的监控工具可能会给你一些提示。|1724451|entityMap|0|LINK|mutability|MUTABLE|url|http://maven.apache.org/surefire/maven-surefire-plugin/faq.html#vm-termination^0|0|C|0|0|0|1|1C|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|Z|8|@$A|10|B|11|H|I]]|9|@]|C|$]]|$1|J|3|-4|5|6|7|12|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|13|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

This part of the <a href="http://maven.apache.org/surefire/maven-surefire-plugin/faq.html#vm-termination" rel="noreferrer">Surefire FAQ</a> could help you:
<blockquote>
Surefire fails with the message &quot;The forked VM terminated without properly saying goodbye&quot;
Surefire does not support tests or any referenced libraries calling System.exit() at any time. If they do so, they are incompatible with surefire and you should probably file an issue with the library/vendor. Alternatively the forked VM could also crash for a number of reasons, which can also make this issue happen. Look for the classical &quot;hs_err*&quot; files indicating VM crashes or examine the log output from running maven when the tests execute. Some &quot;extraordinary&quot; output from crashing processes may be dumped to the console/log. If this happens on a CI environment and only after some time runs there is a fair chance your test suite is leaking some kind of OS-level resource that makes things worse for every run. Regular os-level monitoring tools may give you some indication.
</blockquote>

blocks|key|5251990|text|这可能是因为您在项目中应用了一些更改，而没有更新它们的所有引用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5251991|在我的例子中，我得到这个错误是因为我在我的项目中更新了包的名称，但是我忘记了在TestNG.xml文件中更新它们的引用。通过纠正它，我解决了这个错误。|5251992|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

May be it is because you have applied some changes in your project and did not update their all references.

In my case I was getting this error because I have updated package names in my project but I forgot to update their references in TestNG.xml file. By correcting it, I solved this error.

blocks|key|1484695|text|对我来说，它很好用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1484696|mvn+clean+install+-DskipTests+-e|code-block|syntax|javascript|1484697|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

for me it worked with

<pre><code>mvn clean install -DskipTests -e
</code></pre>

blocks|key|1484707|text|你需要检查你的机器是64位还是32位。如果你的机器是32位的，那么你的内存参数不应该超过4096，即使它应该小于4+GB。但是如果你的机器是64位的，那么安装Java64位，并在mvn.bat中提供指向Java64位安装的JAVA_HOME。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1484708|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You need to check if your machine is 64 bit or 32bit. If your machine is 32 bit then your memory argument should not exceed 4096, even it should be below 4 GB. 
but if your machine is 64 bit then, install Java 64 bit and provide JAVA_HOME in mvn.bat which point to java 64 bit installation.

blocks|key|1484718|text|在我的测试类中的静态成员变量调用一个方法来创建对象(在整个类的测试用例中使用)之后，我遇到了这个错误，并且该方法导致了异常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1484719|//+Object+created+inside+test+class+by+calling+a+static+getter.
//+Exception+thrown+in+getter:
private+static+Object+someObject+=+SomeObject.getObject(...);

//+...+<Object+later+used+in+class>|code-block|syntax|javascript|1484720|一些修复包括在每个测试用例中重新创建对象，并相应地捕获任何异常。或者在@BeforeTest方法中初始化对象并确保它被正确构建。|1484721|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I experienced this error after a static member variable in my test class called a method to create an object (which was used in test cases throughout the class), and the method caused an exception.

<pre><code>// Object created inside test class by calling a static getter.
// Exception thrown in getter:
private static Object someObject = SomeObject.getObject(...);

// ... &lt;Object later used in class&gt;
</code></pre>

Some fixes include recreating the object inside each test case and catching any exceptions accordingly. Or by initializing the object inside an @BeforeTest method and ensuring that it is built properly.

blocks|key|5252084|text|我今天遇到了同样的问题，对我来说，真正的问题在日志中进一步报告了消息Cannot+use+a+threadCount+parameter+less+than+1;+1+>+0。在surefire-plugin配置中添加<threadCount>1</threadCount>时，另一个错误消失了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5252085|完整的插件配置：|5252086|++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-surefire-plugin</artifactId>
++++++++++++<version>2.18.1</version>
++++++++++++<dependencies>
++++++++++++++++<dependency>
++++++++++++++++++++<groupId>org.apache.maven.surefire</groupId>
++++++++++++++++++++<artifactId>surefire-junit47</artifactId>
++++++++++++++++++++<version>2.18.1</version>
++++++++++++++++</dependency>
++++++++++++++++<dependency>
++++++++++++++++++++<groupId>org.apache.maven.surefire</groupId>
++++++++++++++++++++<artifactId>surefire-testng</artifactId>
++++++++++++++++++++<version>2.18.1</version>
++++++++++++++++</dependency>
++++++++++++</dependencies>
++++++++++++<configuration>
++++++++++++++++<threadCount>1</threadCount>
++++++++++++</configuration>
++++++++</plugin>|code-block|syntax|javascript|5252087|...and是的，出于向后兼容性的原因，我在这个测试框架中同时使用了junit和testng。|5252088|entityMap^0|Y|1H|31|S|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|W|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|X|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|P|$]]

I had the same issue today and for me the real problem was reported further up in the log with message <code>Cannot use a threadCount parameter less than 1; 1 &gt; 0</code>.
When adding <code>&lt;threadCount&gt;1&lt;/threadCount&gt;</code> in the surefire-plugin config the other error disappeared.

Full plugin config:

<pre><code> &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.18.1&lt;/version&gt;
 &lt;dependencies&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;org.apache.maven.surefire&lt;/groupId&gt;
 &lt;artifactId&gt;surefire-junit47&lt;/artifactId&gt;
 &lt;version&gt;2.18.1&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;org.apache.maven.surefire&lt;/groupId&gt;
 &lt;artifactId&gt;surefire-testng&lt;/artifactId&gt;
 &lt;version&gt;2.18.1&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;/dependencies&gt;
 &lt;configuration&gt;
 &lt;threadCount&gt;1&lt;/threadCount&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
</code></pre>

...and yes, I am using both junit and testng in this test framework for backward compatibility reasons.

blocks|key|3834925|text|我遇到了同样的问题，并通过添加以下内容解决了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3834926|<argLine>-Xmx1024m+-XX:MaxPermSize=256m</argLine>|code-block|syntax|javascript|3834927|整个插件元素是：|3834928|<plugin>
++<groupId>org.apache.maven.plugins</groupId>
++<artifactId>maven-surefire-plugin</artifactId>
++<configuration>
++++<forkCount>3</forkCount>
++++<reuseForks>true</reuseForks>
++++<argLine>-Xmx1024m+-XX:MaxPermSize=256m</argLine>
++</configuration>
</plugin>|3834929|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I had the same problem and solved by adding: 

<pre class="lang-xml prettyprint-override"><code>&lt;argLine&gt;-Xmx1024m -XX:MaxPermSize=256m&lt;/argLine&gt;
</code></pre>

The whole plugin element is:

<pre class="lang-xml prettyprint-override"><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;forkCount&gt;3&lt;/forkCount&gt;
 &lt;reuseForks&gt;true&lt;/reuseForks&gt;
 &lt;argLine&gt;-Xmx1024m -XX:MaxPermSize=256m&lt;/argLine&gt;
 &lt;/configuration&gt;
&lt;/plugin&gt;
</code></pre>

blocks|key|1724626|text|在我的例子中，这个问题与太长的工作空间路径有关。所以我做了一个路径重构，这解决了我的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1724627|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, the issue was related to workspace path which was to much long. So I did a path refactoring and this solved the issue to me.

blocks|key|3834961|text|当我遇到这个错误时，它是由于我的打开文件限制(ulimit+-n)太低。它(以某种方式)被设置为只有256：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3834962|%25+ulimit+-n
256|code-block|syntax|javascript|3834963|在我增加了限制后，这个错误就消失了：|3834964|%25+ulimit+-n+3072
%25+ulimit+-n+++++
3072|3834965|您的系统可能不允许将限制设置得如此之高。例如，当我尝试使用一个更大的数字时，就会发生这种情况：|3834966|%25+ulimit+-n+3073
ulimit:+setrlimit+failed:+invalid+argument|3834967|或者，这可能低于您现有的限制，您可能面临不同的根本原因。|3834968|entityMap^0|N|9|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|12|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|14|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|V|$]]

When I encountered this error it was due to my ulimit for open files (<code>ulimit -n</code>) being too low. It had (somehow) got set to only 256:

<pre><code>% ulimit -n
256
</code></pre>

The error went away after I increased the limit:

<pre><code>% ulimit -n 3072
% ulimit -n 
3072
</code></pre>

Your system might not allow the limit to be set so high. e.g., this happens when I try to use a larger number:

<pre><code>% ulimit -n 3073
ulimit: setrlimit failed: invalid argument
</code></pre>

Or this might be lower than your existing limit and you could be facing a different root cause.

blocks|key|1724671|text|如果有人包含自定义argLine参数，您必须重新考虑，因为它很可能是内存分配问题的根源。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1724672|例如(我曾经有过)：|1724673|<argLine>XX:MaxPermSize=4096m+${argLine}</argLine>|code-block|syntax|javascript|1724674|现在我使用硬指定的值：|1724675|<argLine>-Xmx1024m+-XX:MaxPermSize=256m</argLine>|1724676|无论出于什么原因，与Surefire集成的应用程序(如Jacoco+)都不需要足够的内存来与构建时发生的测试共存。|1724677|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

If anyone is including a custom argLine argument, you must reconsider because it is likely the source of your issues with the memory allocation.

For Example (I used to have):

<pre><code>&lt;argLine&gt;XX:MaxPermSize=4096m ${argLine}&lt;/argLine&gt;
</code></pre>

Now I use hard specified values:

<pre><code>&lt;argLine&gt;-Xmx1024m -XX:MaxPermSize=256m&lt;/argLine&gt;
</code></pre>

For whatever reason, Applications that integrate with Surefire such as Jacoco, dont request enough memory to coexist with the testing that happens at build time.

blocks|key|3834991|text|在我的例子中，我忘记在pom中添加依赖项：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3834992|++++++<dependency>
++++++++++<groupId>org.aspectj</groupId>
++++++++++<artifactId>aspectjweaver</artifactId>
++++++++++<version>1.8.5</version>
++++++</dependency>|code-block|syntax|javascript|3834993|只需确保您选择了正确的版本(目前1.8.9是最新版本)|3834994|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In my case, I forgot to add the dependency in the pom:

<pre><code> &lt;dependency&gt;
 &lt;groupId&gt;org.aspectj&lt;/groupId&gt;
 &lt;artifactId&gt;aspectjweaver&lt;/artifactId&gt;
 &lt;version&gt;1.8.5&lt;/version&gt;
 &lt;/dependency&gt;
</code></pre>

Just make sure that you pick the right version (as for today 1.8.9 is latest)

blocks|key|1724706|text|当Jenkins在Ubuntu机器上构建时，我遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1724707|/var/log/syslog报告了Out+of+memory:+Kill+process+19557+(java)+score+207+or+sacrifice+child。|offset|length|style|CODE|1724708|I+therefore+gave+the+Ubuntu+machine+more+swap+space。从那时起，这个问题就消失了。|1724709|entityMap|0|LINK|mutability|MUTABLE|url|https://askubuntu.com/a/178726/132098^0|0|0|F|I|1X|0|0|1F|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]|$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

I ran into this problem during Jenkins builds on an Ubuntu machine.

<code>/var/log/syslog</code> reported <code>Out of memory: Kill process 19557 (java) score 207 or sacrifice child</code>.

<a href="https://askubuntu.com/a/178726/132098">I therefore gave the Ubuntu machine more swap space</a>. Since then, the problem is gone.

blocks|key|5252204|text|我也经历过这种情况，但在我的例子中，我为黄瓜编写了一个定制的钩子。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5252205|public+class+MappingFormatter+implements+gherkin.formatter.Formatter+{|code-block|syntax|javascript|5252206|..。|5252207|我的方法之一是产生一个空指针异常，它导致surefire退出而不记录错误。|5252208|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I also experienced this - but in my case I had written a custom hook for cucumber 

<pre><code>public class MappingFormatter implements gherkin.formatter.Formatter {
</code></pre>

...

one of my methods was producing a Null pointer exception, which caused the surefire to exit without logging the error.

blocks|key|3835040|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3835041|派生的VM在没有正确说再见的情况下终止。虚拟机崩溃或System.exit被调用|blockquote|3835042|3835043|3835044|防止此错误的方法是以管理员身份运行IDE。|3835045|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|J|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|K|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|L|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|M|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|N|7|@]|8|@]|9|$]]|$1|H|3|-4|4|5|6|O|7|@]|8|@]|9|$]]]|I|$]]

<blockquote>
 The forked VM terminated without saying properly goodbye. VM crash or System.exit called
</blockquote>

The way to prevent this error is to run your IDE as Administrator.

blocks|key|5252253|text|在JDK+1.8.0_65上使用Jacoco插件运行mvn命令时遇到类似的问题|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|5252254|[INFO]
A+fatal+error+has+been+detected+by+the+Java+Runtime+Environment:

JRE+version:+Java(TM)+SE+Runtime+Environment+(8.0_65-b17)+(build+1.8.0_65-b17).........
Problematic+frame:
PhaseIdealLoop::build_loop_late_post(Node*)%2B0x144
............
............
[ERROR]+Failed+to+execute+goal+org.apache.maven.plugins:maven-surefire-plugin:2.19:test+(default-test)+on+project+

+The+forked+VM+terminated+without+properly+saying+goodbye.+VM+crash+or+System.exit+called?|code-block|syntax|javascript|5252255|在JDK+https://bugs.openjdk.java.net/browse/JDK-8081379中有一个错误。|5252256|解决方案是使用参数-XX:-UseLoopPredicate运行mvn全新安装。|5252257|或者只是更新JDK+(我认为较新的次要版本可以工作)|5252258|entityMap|0|LINK|mutability|MUTABLE|url|https://bugs.openjdk.java.net/browse/JDK-8081379^0|B|2|0|0|5|1C|0|0|9|L|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|M|3|N|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|19|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

Had similar problem when running mvn command with Jacoco plugin on JDK 1.8.0_65

<pre><code>[INFO]
A fatal error has been detected by the Java Runtime Environment:

JRE version: Java(TM) SE Runtime Environment (8.0_65-b17) (build 1.8.0_65-b17).........
Problematic frame:
PhaseIdealLoop::build_loop_late_post(Node*)+0x144
............
............
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19:test (default-test) on project 

 The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
</code></pre>

There was a bug in JDK <a href="https://bugs.openjdk.java.net/browse/JDK-8081379" rel="noreferrer">https://bugs.openjdk.java.net/browse/JDK-8081379</a> 

And the solution was to run mvn clean install with param -XX:-UseLoopPredicate 

Or just make an update to JDK (I think newer minor version works)

blocks|key|1724832|text|最近，travis终止了一个测试的执行(没有更改任何相关的东西(以及开发人员机器上的成功构建！))，因此BUILD+FAILURE。其中一个原因是这样的(请参阅@agudian答案)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1724833|1724834|+Surefire不支持调用System.exit()`的测试或任何引用的库|blockquote|1724835|1724836|1724837|(因为测试类实际上称为System.exit(-1))。|CODE|1724838|相反，|1724839|使用简单的return语句会有所帮助。为了让travis再次高兴，我还必须添加@|ordered-list-item|1724840|提供的surefire参数(<argLine>)。(此外，我必须删除-XX:MaxPermSize=256m才能在我的一个桌面上构建)|1724841|1724842|只做两件事中的一件是行不通的。|1724843|有关更多背景信息，请阅读When+should+we+call+System.exit+in+Java。|1724844|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/3715967/when-should-we-call-system-exit-in-java^0|3|6|1G|D|0|0|0|0|0|B|F|0|0|5|6|0|E|9|Y|K|0|0|0|C|13|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|1E|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1H|8|@$9|1I|A|1J|B|N]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1K|8|@]|D|@]|E|$]]|$1|Q|3|R|5|S|7|1L|8|@$9|1M|A|1N|B|N]]|D|@]|E|$]]|$1|T|3|U|5|S|7|1O|8|@$9|1P|A|1Q|B|N]|$9|1R|A|1S|B|N]]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1T|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|1U|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|1V|8|@]|D|@$9|1W|A|1X|1|1Y]]|E|$]]|$1|10|3|-4|5|6|7|1Z|8|@]|D|@]|E|$]]]|11|$12|$5|13|14|15|E|$16|17]]]]

Recently travis killed the execution of a test (without having changed anything related (and successful builds on developer machines!)), thus BUILD FAILURE.
One of the causes was this (see @agudian answer):

<blockquote>
 Surefire does not support tests or any referenced libraries calling System.exit()`
</blockquote>

(since the test class indeed called <code>System.exit(-1)</code>).

<ol>
<li>Using a simple <code>return</code> statement instead helps. </li>
<li>To make travis happy again, I also had to add the surefire parameters (<code>&lt;argLine&gt;</code>) provided by @xiaohuo. (also, I had to remove <code>-XX:MaxPermSize=256m</code> to be able to build on one of my desktops)</li>
</ol>

Doing only one of the two things didn't worked.

For more background read <a href="https://stackoverflow.com/questions/3715967/when-should-we-call-system-exit-in-java">When should we call System.exit in Java</a>.

blocks|key|1480658|text|这也可能是由于一个完全不同的问题造成的。例如，在我的例子中，我们的Jenkins构建在没有任何原因的情况下执行测试时间歇性地失败。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1480659|我筛选了我们的测试，以寻找任何System.exit()的出现，但没有。|offset|length|style|CODE|1480660|经过进一步的挖掘，我发现这可能是由于JDK错误造成的，这可能导致了这种回归。|1480661|JDK-6675699+|1480662|我仍然在努力使这个修复在我们的构建，将回来，并更新线程再次。|1480663|entityMap|0|LINK|mutability|MUTABLE|url|https://bugs.openjdk.java.net/browse/JDK-6675699^0|0|F|D|0|0|0|C|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@$D|11|E|12|1|13]]|A|$]]|$1|L|3|M|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

This could also happen due to a totally different issue. For example in my case our Jenkins build was failing intermittently while executing tests without any reason.

I sifted through our tests to find any occurrence of <code>System.exit()</code> but there was none. 

After more digging I found out that this could be happening because of a JDK bug which could have caused this regression. 

<a href="https://bugs.openjdk.java.net/browse/JDK-6675699" rel="nofollow noreferrer" title="JDK-6675699">JDK-6675699 </a>

I am still working on making this fix in our builds, will come back and update the thread again.

blocks|key|1724911|text|这可能是由于内存不足造成的。确保在运行mvn时没有任何应用程序在后台运行。在我的例子中，Firefox在后台运行，内存使用率很高。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1724912|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This may occur due to inadequate memory. Make sure you don't have any applications running on background while running mvn. In my case Firefox was running on background with high memory usage.

blocks|key|3835197|text|这肯定行得通……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3835198|在POM文件中添加以下代码行，并给出一个构建。|3835199|<plugin>
++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++<artifactId>maven-surefire-plugin</artifactId>
++++++++++<version>2.19.1</version>
++++++++++<configuration>
++++++++++++<trimStackTrace>false</trimStackTrace>
++++++++++++<includes>
++++++++++++++<include>**/*Test.class</include>
++++++++++++</includes>
++++++++++</configuration>
++++++++</plugin>|code-block|syntax|javascript|3835200|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

This will work definitely.....

Add the below lines in the POM file and give a build.

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.19.1&lt;/version&gt;
 &lt;configuration&gt;
 &lt;trimStackTrace&gt;false&lt;/trimStackTrace&gt;
 &lt;includes&gt;
 &lt;include&gt;**/*Test.class&lt;/include&gt;
 &lt;/includes&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
</code></pre>

blocks|key|3835210|text|“原因:+java.util.concurrent.ExecutionException:+java.lang.RuntimeException:派生的VM在没有正确说再见的情况下终止。VM崩溃或System.exit调用？”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3835211|如果您使用非兼容版本的java，则可能会出现此问题。Like使用新版本的java，而代码则支持其他版本。|offset|length|style|BOLD|3835212|entityMap^0|0|5|A|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

"Caused by: java.util.concurrent.ExecutionException: java.lang.RuntimeException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?"

This issue can be occur if you use non compatible version of java. Like uses new version of java while code support some other version.

blocks|key|1480699|text|当我试图在运行JAVA+=+1.8的Windows10环境中编译设置为1.7的maven项目时，我确实遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1480700|我通过将java版本从1.7改为1.8解决了这个问题，如下所示。|1480701|+<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-compiler-plugin</artifactId>
++++<version>3.3</version>
++++<configuration>
++++++<source>1.8</source>
++++++<target>1.8</target>
++++</configuration>
++</plugin>|code-block|syntax|javascript|1480702|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Did encounter the same problem as I was trying to compile a maven project set to 1.7 on a windows 10 environment running JAVA = 1.8. 

I resolved it by changing the java version from 1.7 to 1.8 as shown below.

<pre><code> &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-compiler-plugin&lt;/artifactId&gt;
 &lt;version&gt;3.3&lt;/version&gt;
 &lt;configuration&gt;
 &lt;source&gt;1.8&lt;/source&gt;
 &lt;target&gt;1.8&lt;/target&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
</code></pre>

blocks|key|3835268|text|最近，我在使用竹子构建我的容器化jar应用程序时遇到了这个错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3835269|org.apache.maven.surefire.booter.SurefireBooterForkException：|3835270|分支虚拟机在未正确说再见的情况下终止|blockquote|3835271|3835272|3835273|经过几个小时的研究，我把它修好了。我想在这里分享我的解决方案会很有用。|3835274|因此，每当竹子在docker容器中为java应用程序运行mvn+clean+package命令时，都会发生错误。我不是Maven专家，但麻烦在于Surefire和Junit4插件包含在spring-boot中作为maven依赖项。|offset|length|style|CODE|3835275|要修复它，您需要替换Junit5的Junit4，并覆盖pom.xml中的Surefire插件。|3835276|1.内侧弹簧套从属插入排除：|3835277|<dependency>
++++<groupId>org.springframework.boot</groupId>
++++<artifactId>spring-boot-starter-test</artifactId>
++++<scope>test</scope>
++++
</dependency>|code-block|syntax|javascript|3835278|3835279|添加新的Junit5依赖项：|ordered-list-item|3835280|3835281|<dependency>
++++<groupId>org.junit.jupiter</groupId>
++++<artifactId>junit-jupiter-api</artifactId>
++++<scope>test</scope>
</dependency>
<dependency>
++++<groupId>org.junit.jupiter</groupId>
++++<artifactId>junit-jupiter-engine</artifactId>
++++<version>5.1.0</version>
++++<scope>test</scope>
</dependency>
<dependency>
++++<groupId>org.junit.vintage</groupId>
++++<artifactId>junit-vintage-engine</artifactId>
++++<version>5.1.0</version>
++++<scope>test</scope>
</dependency>
<dependency>
++++<groupId>org.junit.platform</groupId>
++++<artifactId>junit-platform-launcher</artifactId>
++++<version>1.1.0</version>
++++<scope>test</scope>
</dependency>
<dependency>
++++<groupId>org.junit.platform</groupId>
++++<artifactId>junit-platform-runner</artifactId>
++++<version>1.1.0</version>
++++<scope>test</scope>
</dependency>
<dependency>
++++<groupId>org.junit.platform</groupId>
++++<artifactId>junit-platform-surefire-provider</artifactId>
++++<version>1.1.0</version>
++++<scope>test</scope>
</dependency>|3835282|3835283|在插件部分插入新插件|3835284|3835285|<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-failsafe-plugin</artifactId>
</plugin>
<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-surefire-plugin</artifactId>
++++<version>2.19.1</version>
++++<dependencies>
++++++++<dependency>
++++++++++++<groupId>org.junit.platform</groupId>
++++++++++++<artifactId>junit-platform-surefire-provider</artifactId>
++++++++++++<version>1.1.0</version>
++++++++</dependency>
++++++++<dependency>
++++++++++++<groupId>org.junit.jupiter</groupId>
++++++++++++<artifactId>junit-jupiter-engine</artifactId>
++++++++++++<version>5.1.0</version>
++++++++</dependency>
++++</dependencies>
</plugin>|3835286|这应该足以修复竹制建筑。别忘了还要转换所有支持Junit5的Junit4测试。|3835287|entityMap^0|0|0|0|0|0|0|S|H|0|R|7|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1H|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1I|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1L|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1M|8|@$M|1N|N|1O|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1P|8|@$M|1Q|N|1R|O|P]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1S|8|@]|9|@]|A|$]]|$1|U|3|V|5|W|7|1T|8|@]|9|@]|A|$X|Y]]|$1|Z|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|10|3|11|5|12|7|1V|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]|$1|14|3|15|5|W|7|1X|8|@]|9|@]|A|$X|Y]]|$1|16|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|17|3|18|5|12|7|1Z|8|@]|9|@]|A|$]]|$1|19|3|-4|5|6|7|20|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|W|7|21|8|@]|9|@]|A|$X|Y]]|$1|1C|3|1D|5|6|7|22|8|@]|9|@]|A|$]]|$1|1E|3|-4|5|6|7|23|8|@]|9|@]|A|$]]]|1F|$]]

I recently stuck in with this error while building my containerized jar applications with Bamboo:

<blockquote>
 org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye
</blockquote>

After many hours of researching I fixed it. And I thought it would be useful to share my solution here.

So the error happen every time when bamboo run <code>mvn clean package</code> command for java applications in the docker containers. I am no Maven expert but the trouble was in Surefire and Junit4 plugins included in spring-boot as maven dependency. 

To fix it you need to replace Junit4 for Junit5 and override Surefire plugin in you <code>pom.xml</code>.

1.Inside spring boot dependency insert exclusion:

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
 &lt;artifactId&gt;spring-boot-starter-test&lt;/artifactId&gt;
 &lt;scope&gt;test&lt;/scope&gt;
 &lt;!-- FIX BAMBOO DEPLOY&gt;
 &lt;exclusions&gt;
 &lt;exclusion&gt;
 &lt;groupId&gt;junit&lt;/groupId&gt;
 &lt;artifactId&gt;junit&lt;/artifactId&gt;
 &lt;/exclusion&gt;
 &lt;/exclusions&gt;
 &lt;!----&gt;
&lt;/dependency&gt;
</code></pre>

2. Add new Junit5 dependencies:

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;org.junit.jupiter&lt;/groupId&gt;
 &lt;artifactId&gt;junit-jupiter-api&lt;/artifactId&gt;
 &lt;scope&gt;test&lt;/scope&gt;
&lt;/dependency&gt;
&lt;dependency&gt;
 &lt;groupId&gt;org.junit.jupiter&lt;/groupId&gt;
 &lt;artifactId&gt;junit-jupiter-engine&lt;/artifactId&gt;
 &lt;version&gt;5.1.0&lt;/version&gt;
 &lt;scope&gt;test&lt;/scope&gt;
&lt;/dependency&gt;
&lt;dependency&gt;
 &lt;groupId&gt;org.junit.vintage&lt;/groupId&gt;
 &lt;artifactId&gt;junit-vintage-engine&lt;/artifactId&gt;
 &lt;version&gt;5.1.0&lt;/version&gt;
 &lt;scope&gt;test&lt;/scope&gt;
&lt;/dependency&gt;
&lt;dependency&gt;
 &lt;groupId&gt;org.junit.platform&lt;/groupId&gt;
 &lt;artifactId&gt;junit-platform-launcher&lt;/artifactId&gt;
 &lt;version&gt;1.1.0&lt;/version&gt;
 &lt;scope&gt;test&lt;/scope&gt;
&lt;/dependency&gt;
&lt;dependency&gt;
 &lt;groupId&gt;org.junit.platform&lt;/groupId&gt;
 &lt;artifactId&gt;junit-platform-runner&lt;/artifactId&gt;
 &lt;version&gt;1.1.0&lt;/version&gt;
 &lt;scope&gt;test&lt;/scope&gt;
&lt;/dependency&gt;
&lt;dependency&gt;
 &lt;groupId&gt;org.junit.platform&lt;/groupId&gt;
 &lt;artifactId&gt;junit-platform-surefire-provider&lt;/artifactId&gt;
 &lt;version&gt;1.1.0&lt;/version&gt;
 &lt;scope&gt;test&lt;/scope&gt;
&lt;/dependency&gt;
</code></pre>

3. Insert new plugin inside plugins section

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-failsafe-plugin&lt;/artifactId&gt;
&lt;/plugin&gt;
&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.19.1&lt;/version&gt;
 &lt;dependencies&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;org.junit.platform&lt;/groupId&gt;
 &lt;artifactId&gt;junit-platform-surefire-provider&lt;/artifactId&gt;
 &lt;version&gt;1.1.0&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;org.junit.jupiter&lt;/groupId&gt;
 &lt;artifactId&gt;junit-jupiter-engine&lt;/artifactId&gt;
 &lt;version&gt;5.1.0&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;/dependencies&gt;
&lt;/plugin&gt;
</code></pre>

That's should be enough to repair bamboo builds. Don't forget also transform all Junit4 tests to support Junit5.

blocks|key|5252478|text|我有非常类似的问题(Maven+build+and+maven-failsafe-plugin+-+The+forked+VM+terminated+without+properly+saying+goodbye)，并找到了三个对我有效的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5252479|问题描述|5252480|问题出在maven插件maven-surefire-plugin仅在2.20.1和2.21.0版本中。我检查过了，您使用的是2.20.1版。|style|BOLD|5252481|解决方案1|5252482|将插件版本升级到2.22.0。在pom.xml中添加|5252483|<plugin>
++<groupId>org.apache.maven.plugins</groupId>
++<artifactId>maven-surefire-plugin</artifactId>
++<version>2.22.0</version>
</plugin>|code-block|syntax|javascript|5252484|解决方案2|5252485|将插件版本降级到2.20。在pom.xml中添加|5252486|<plugin>
++<groupId>org.apache.maven.plugins</groupId>
++<artifactId>maven-surefire-plugin</artifactId>
++<version>2.20</version>
</plugin>|5252487|解决方案3|5252488|使用插件配置testFailureIgnore.在pom.xml中添加|5252489|<plugin>
++<groupId>org.apache.maven.plugins</groupId>
++<artifactId>maven-surefire-plugin</artifactId>
++<configuration>
++++<testFailureIgnore>true</testFailureIgnore>
++</configuration>
</plugin>|5252490|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/46831762/maven-build-and-maven-failsafe-plugin-the-forked-vm-terminated-without-properl/51099726#51099726^0|A|2O|0|0|0|B|L|0|0|8|6|G|7|0|0|0|8|4|E|7|0|0|0|6|H|P|7|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@$A|1D|B|1E|1|1F]]|C|$]]|$1|D|3|E|5|6|7|1G|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1H|8|@$A|1I|B|1J|H|I]]|9|@]|C|$]]|$1|J|3|K|5|6|7|1K|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|1L|8|@$A|1M|B|1N|H|I]|$A|1O|B|1P|H|I]]|9|@]|C|$]]|$1|N|3|O|5|P|7|1Q|8|@]|9|@]|C|$Q|R]]|$1|S|3|T|5|6|7|1R|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|1S|8|@$A|1T|B|1U|H|I]|$A|1V|B|1W|H|I]]|9|@]|C|$]]|$1|W|3|X|5|P|7|1X|8|@]|9|@]|C|$Q|R]]|$1|Y|3|Z|5|6|7|1Y|8|@]|9|@]|C|$]]|$1|10|3|11|5|6|7|1Z|8|@$A|20|B|21|H|I]|$A|22|B|23|H|I]]|9|@]|C|$]]|$1|12|3|13|5|P|7|24|8|@]|9|@]|C|$Q|R]]|$1|14|3|-4|5|6|7|25|8|@]|9|@]|C|$]]]|15|$16|$5|17|18|19|C|$1A|1B]]]]

I have very similar problem (<a href="https://stackoverflow.com/questions/46831762/maven-build-and-maven-failsafe-plugin-the-forked-vm-terminated-without-properl/51099726#51099726">Maven build and maven-failsafe-plugin - The forked VM terminated without properly saying goodbye</a>) and found three solutions which working for me:

<h3>Problem description</h3>

Problem is with maven plugin maven-surefire-plugin only in version 2.20.1 and 2.21.0. I checked and you use version 2.20.1.

<h2>Solution 1</h2>

Upgrade plugin version to 2.22.0. Add in pom.xml:

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.22.0&lt;/version&gt;
&lt;/plugin&gt;
</code></pre>

<h2>Solution 2</h2>

Downgrade plugin version to 2.20. Add in pom.xml:

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.20&lt;/version&gt;
&lt;/plugin&gt;
</code></pre>

<h2>Solution 3</h2>

Use plugin configuration testFailureIgnore. Add in pom.xml:

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;testFailureIgnore&gt;true&lt;/testFailureIgnore&gt;
 &lt;/configuration&gt;
&lt;/plugin&gt;
</code></pre>

blocks|key|3835373|text|我遇到过这样一个案例，所有的答案都没有解决这个问题。它使用的是一个遗留应用程序，该应用程序恰好使用了log4j和SLF4J/logback。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3835374|前一种情况:从clean+test内部启动时，Eclipse构建运行良好，但在命令行启动时，会出现此错误。在CircleCI上构建的CI也运行得很好。|offset|length|style|CODE|3835375|我所做的:出于纯粹的猜测，我配置了一个适当的logback-test.xml并降低了日志记录的繁琐程度。瞧，我不再遇到这个错误，我现在可以从命令行构建项目(以及发生此错误的模块)。|3835376|我的观点是，日志框架的使用或配置方式可能是另一种解释。|3835377|这真的是log4j和logback之间的冲突吗？或者仅仅是测试产生的大量日志以某种方式溢出了命令行缓冲区？我不知道。这对我来说仍然是个谜。|3835378|entityMap^0|0|7|A|0|M|G|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|O|$]]

I've met a case when none of the answers provided solved the issue. It was with a legacy application which happens to be using log4j and SLF4J/logback.

The previous situation: <code>clean test</code> builds were running fine when launched from within Eclipse, but when launched in the command line, this error occurred. CI builds on CircleCI ran fine too.

What I did: out of pure guess, is configure a proper <code>logback-test.xml</code> and dial down the verbosity of the logging. Lo and behold, I no longer experienced this error and I can now build the project (as well as the module in which this error was occurring) from the command line.

My point is that the way that the logging frameworks are used or configured may be another explanation.

Was it really a conflict between log4j and logback ? Or was it just that the high volume of logging produced by the tests somehow overflowed a command line buffer? I don't know. It remains a mystery to me.

blocks|key|3835397|text|在我的例子中，这个问题与输出到IntelliJ+IDEA控制台(OS+Windows10)的日志太长有关。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3835398|命令：|3835399|mvn+clean+install|code-block|syntax|javascript|3835400|这个命令解决了我的问题：|3835401|mvn+clean+install+>+log-file.log|3835402|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

In my case the issue was related to too long log outputting into IntelliJ IDEA console (OS windows 10).
 Command:

<pre><code>mvn clean install
</code></pre>

This command solved the issue to me:
 

<pre><code>mvn clean install &gt; log-file.log
</code></pre>

blocks|key|5252563|text|我对这个问题的解决方案是关闭那该死的chrome浏览器，它阻塞了我计算机的内存|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5252564|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

My resolution to this issue was to Close the damn chrome browser which was choking my computer's memory

blocks|key|1480781|text|截至今天(2018年10月30日)，我们注意到Jenkins中的构建因此错误而崩溃。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1480782|该错误具有误导性，需要查看target/surefire-reports/中的转储输出才能看到以下错误消息：|offset|length|style|CODE|1480783|Error:+Could+not+find+or+load+main+class+org.apache.maven.surefire.booter.ForkedBooter|code-block|syntax|javascript|1480784|这将我带到下面的SO+post，它提到了OpenJDK+181中可能存在的一个错误：Maven+surefire+could+not+find+ForkedBooter+class|1480785|这篇文章中的任何一个修复都解决了我的问题。具体地说，我使用了以下两种方法之一：|1480786|Spring+Boot从docker容器maven:3.5.4-jdk-8切换到maven:3.5.4-jdk-8-alpine|1480787|Overriding+Spring+Boot的类加载器，详情如下：https://stackoverflow.com/a/50661649/1228408|unordered-list-item|1480788|1480789|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/53010200/maven-surefire-could-not-find-forkedbooter-class|1|https://stackoverflow.com/a/50661649/1228408^0|0|D|O|0|0|16|1C|0|0|0|K|H|14|O|0|X|18|1|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|1A|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1B|8|@]|9|@$D|1C|E|1D|1|1E]]|A|$]]|$1|O|3|P|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1G|8|@$D|1H|E|1I|F|G]|$D|1J|E|1K|F|G]]|9|@]|A|$]]|$1|S|3|T|5|U|7|1L|8|@]|9|@$D|1M|E|1N|1|1O]]|A|$]]|$1|V|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]|14|$5|Z|10|11|A|$12|15]]]]

As of today (10/30/2018), we noticed our builds breaking in Jenkins with this error.

The error is a bit misleading and required looking at the output of the dump in <code>target/surefire-reports/</code> to see the following error message:

<pre><code>Error: Could not find or load main class org.apache.maven.surefire.booter.ForkedBooter
</code></pre>

That lead me to the following SO post which mentions a possible bug in OpenJDK 181: <a href="https://stackoverflow.com/questions/53010200/maven-surefire-could-not-find-forkedbooter-class">Maven surefire could not find ForkedBooter class</a>

Either of the fixes in that post solve my issue. To be specific, I used either one of these:

<ol>
<li>Switching from building in the docker container <code>maven:3.5.4-jdk-8</code> to <code>maven:3.5.4-jdk-8-alpine</code></li>
<li>Overriding Spring Boot's class loader detailed here: <a href="https://stackoverflow.com/a/50661649/1228408">https://stackoverflow.com/a/50661649/1228408</a></li>
</ol>

blocks|key|1725202|text|您可以设置java选项|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1725203|SET+JAVA_OPTS='-Xmx1024m'+XX:%2BUseLoopPredicate|offset|length|style|CODE|1725204|mvn+clean+install|1725205|entityMap^0|0|0|1A|0|0|H|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

You can set java options

<code>SET JAVA_OPTS='-Xmx1024m' XX:+UseLoopPredicate</code>

<code>mvn clean install</code>

blocks|key|1485037|text|也面临着同样的问题，ubuntu上的java+8|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1485038|然后偶然发现了https://stackoverflow.com/a/53016532/1676516|offset|length|1485039|这似乎是带有java+8+https://issues.apache.org/jira/browse/SUREFIRE-1588的surefire插件版本2.22.1中最近的一个错误。|1485040|已通过本地mvn设置~/.m2/settings.xml遵循建议的解决方法|style|CODE|1485041|<profiles>
++++<profile>
++++++++<id>SUREFIRE-1588</id>
++++++++<activation>
++++++++++++<activeByDefault>true</activeByDefault>
++++++++</activation>
++++++++<properties>
++++++++++++<argLine>-Djdk.net.URLClassPath.disableClassPathURLCheck=true</argLine>
++++++++</properties>
++++</profile>
</profiles>|code-block|syntax|javascript|1485042|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/53016532/1676516|1|https://issues.apache.org/jira/browse/SUREFIRE-1588^0|0|7|18|0|0|D|1F|1|0|A|I|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@$D|16|E|17|1|18]]|A|$]]|$1|H|3|I|5|6|7|19|8|@$D|1A|E|1B|J|K]]|9|@]|A|$]]|$1|L|3|M|5|N|7|1C|8|@]|9|@]|A|$O|P]]|$1|Q|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]|Y|$5|T|U|V|A|$W|Z]]]]

Was just facing the same problem, java 8 on ubuntu

then came across <a href="https://stackoverflow.com/a/53016532/1676516">https://stackoverflow.com/a/53016532/1676516</a>

It seems a recent bug in the surefire plugin version 2.22.1 with java 8 <a href="https://issues.apache.org/jira/browse/SUREFIRE-1588" rel="noreferrer">https://issues.apache.org/jira/browse/SUREFIRE-1588</a> 

followed the suggested workaround through local mvn settings <code>~/.m2/settings.xml</code>

<pre><code>&lt;profiles&gt;
 &lt;profile&gt;
 &lt;id&gt;SUREFIRE-1588&lt;/id&gt;
 &lt;activation&gt;
 &lt;activeByDefault&gt;true&lt;/activeByDefault&gt;
 &lt;/activation&gt;
 &lt;properties&gt;
 &lt;argLine&gt;-Djdk.net.URLClassPath.disableClassPathURLCheck=true&lt;/argLine&gt;
 &lt;/properties&gt;
 &lt;/profile&gt;
&lt;/profiles&gt;
</code></pre>

blocks|key|1725264|text|在pom.xml中设置它对我来说很有效。但是您应该查看文档中的其他变通方法https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1725265|+++++++<plugin>

++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-surefire-plugin</artifactId>
++++++++++++<configuration>
++++++++++++++++
++++++++++++++++<useSystemClassLoader>true</useSystemClassLoader>
++++++++++++++++<useManifestOnlyJar>false</useManifestOnlyJar>
++++++++++++</configuration>
++++++++</plugin>|code-block|syntax|javascript|1725266|entityMap|0|LINK|mutability|MUTABLE|url|https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html^0|11|2B|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

Setting this in pom.xml worked for me.
But you should check the documentation for other workarounds
<a href="https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html" rel="nofollow noreferrer">https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html</a>

<pre><code> &lt;plugin&gt;

 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;!--these strange settings fixes a chrash and dumpstream from surefire when run from command line
 Caused by: java.lang.ClassNotFoundException: org.apache.maven.surefire.booter.ForkedBooter
 --&gt;
 &lt;useSystemClassLoader&gt;true&lt;/useSystemClassLoader&gt;
 &lt;useManifestOnlyJar&gt;false&lt;/useManifestOnlyJar&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
</code></pre>

blocks|key|5252661|text|在Windows+(OpenJDK11，Maven3.6.0，SUREFIRE+3.0.0-M1)上，我得到了根本原因：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5252662|#+Created+at+2018-11-14T14:28:15.629
OpenJDK+64-Bit+Server+VM+warning:+INFO:+os::commit_memory(0x00000006c7500000,+522190848,+0)+failed;+error='The+paging+file+is+too+small+for+this+operation+to+complete'+(DOS+error/errno=1455)|code-block|syntax|javascript|5252663|并通过增加分页文件大小来解决，例如像this。|offset|length|5252664|entityMap|0|LINK|mutability|MUTABLE|url|https://www.online-tech-tips.com/computer-tips/simple-ways-to-increase-your-computers-performace-configuring-the-paging-file/^0|0|0|I|4|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

On Windows (OpenJDK11, Maven 3.6.0, SUREFIRE 3.0.0-M1) I got that root cause:

<pre><code># Created at 2018-11-14T14:28:15.629
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00000006c7500000, 522190848, 0) failed; error='The paging file is too small for this operation to complete' (DOS error/errno=1455)
</code></pre>

and resolved by increasing the paging file size, e.g like <a href="https://www.online-tech-tips.com/computer-tips/simple-ways-to-increase-your-computers-performace-configuring-the-paging-file/" rel="nofollow noreferrer">this</a>.

blocks|key|1480833|text|尝试了以上所有方法，都不起作用。下面的解决方案对我很有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1480834|<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.19.1</version>
<configuration>
++++<argLine>-Dfile.encoding=UTF-8</argLine>
</configuration>|code-block|syntax|javascript|1480835|​|1480836|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

tried all above, didn't work. below solution works for me:

<pre><code>&lt;plugin&gt;
&lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
&lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
&lt;version&gt;2.19.1&lt;/version&gt;
&lt;configuration&gt;
 &lt;argLine&gt;-Dfile.encoding=UTF-8&lt;/argLine&gt;
&lt;/configuration&gt;
</code></pre>

blocks|key|1725328|text|关闭maven-surefile的useSystemClassLoader+-插件应该会有帮助|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1725329|<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-surefire-plugin</artifactId>
++++<version>2.22.0</version>
++++<configuration>
++++++++<useSystemClassLoader>false</useSystemClassLoader>
++++</configuration>
</plugin>|code-block|syntax|javascript|1725330|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Turn off useSystemClassLoader of maven-surefile-plugin should help
<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.22.0&lt;/version&gt;
 &lt;configuration&gt;
 &lt;useSystemClassLoader&gt;false&lt;/useSystemClassLoader&gt;
 &lt;/configuration&gt;
&lt;/plugin&gt;
</code></pre>

blocks|key|5252728|text|我遇到了同样的问题，并通过使用Oracle的Java+8而不是Openjdk的Java+10解决了这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5252729|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same issue and solved by using Java 8 from Oracle instead of Java 10 from Openjdk

blocks|key|1485115|text|我在Jenkins+Docker容器中也遇到了这个问题(尝试了jenkins:lts，jenkins，jenkins:slim和jenkins:slim-lts。我不想遍历所有存储库并更新每个项目的pom，所以我只将disableClassPathURLCheck添加到maven命令行调用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1485116|mvn+test+-DargLine="-Djdk.net.URLClassPath.disableClassPathURLCheck=true"|code-block|syntax|javascript|1485117|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I ran into this problem as well in a Jenkins Docker container (tried jenkins:lts, jenkins, jenkins:slim and jenkins:slim-lts. I didn't want to go through all repositories and update the pom for each project, so I just added the disableClassPathURLCheck to the maven command line call:

<pre><code>mvn test -DargLine="-Djdk.net.URLClassPath.disableClassPathURLCheck=true"
</code></pre>

blocks|key|5252805|text|使用maven+surefire+2.21.0，我解决了将reuseForks选项的值从true更改为false的问题：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|5252806|<build>
++++<plugins>
++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-surefire-plugin</artifactId>
++++++++++++<version>2.21.0</version>
++++++++++++<configuration>
++++++++++++++++<reuseForks>false</reuseForks>
++++++++++++</configuration>
++++++++</plugin>
++++</plugins>
</build>|code-block|syntax|javascript|5252807|我在build下的整个配置节如下所示：|5252808|<build>
++++<plugins>
++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-surefire-plugin</artifactId>
++++++++++++<version>2.21.0</version>
++++++++++++<configuration>
++++++++++++++++<testFailureIgnore>true</testFailureIgnore>
++++++++++++++++<skip>false</skip>
++++++++++++++++<reuseForks>false</reuseForks>
++++++++++++++++<argLine>-Xmx1024m+-XX:MaxPermSize=256m</argLine>
++++++++++++++++<argLine>-Dfile.encoding=UTF-8</argLine>
++++++++++++++++<useSystemClassLoader>false</useSystemClassLoader>
++++++++++++++++<includes>
++++++++++++++++++++
++++++++++++++++++++<include>**/directory/Test*.java</include>
++++++++++++++++</includes>
++++++++++++</configuration>
++++++++</plugin>
++++</plugins>
</build>|5252809|entityMap^0|T|A|18|4|1F|5|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|D]|$9|W|A|X|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|Y|8|@]|E|@]|F|$J|K]]|$1|L|3|M|5|6|7|Z|8|@]|E|@]|F|$]]|$1|N|3|O|5|I|7|10|8|@]|E|@]|F|$J|K]]|$1|P|3|-4|5|6|7|11|8|@]|E|@]|F|$]]]|Q|$]]

Using maven surefire 2.21.0 I solved the issue changing the <code>reuseForks</code> option value from true to false: 

<pre><code>&lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.21.0&lt;/version&gt;
 &lt;configuration&gt;
 &lt;reuseForks&gt;false&lt;/reuseForks&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
&lt;/build&gt;
</code></pre>

My whole config section under build looked like:

<pre><code>&lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.21.0&lt;/version&gt;
 &lt;configuration&gt;
 &lt;testFailureIgnore&gt;true&lt;/testFailureIgnore&gt;
 &lt;skip&gt;false&lt;/skip&gt;
 &lt;reuseForks&gt;false&lt;/reuseForks&gt;
 &lt;argLine&gt;-Xmx1024m -XX:MaxPermSize=256m&lt;/argLine&gt;
 &lt;argLine&gt;-Dfile.encoding=UTF-8&lt;/argLine&gt;
 &lt;useSystemClassLoader&gt;false&lt;/useSystemClassLoader&gt;
 &lt;includes&gt;
 &lt;!--Test* classes for the app testing --&gt;
 &lt;include&gt;**/directory/Test*.java&lt;/include&gt;
 &lt;/includes&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
&lt;/build&gt;
</code></pre>

blocks|key|3835709|text|测试中使用的派生JVM内存不足。解决方案是禁用派生JVM并在主JVM上运行测试，以确保您有足够的内存，或者传递args以增加派生的JVM的内存|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3835710|查看此answer中的解决方案|offset|length|3835711|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/49448372/5052928^0|0|3|6|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

The forked JVM used in the test is running out of memory.
The solution would be to either disable forking a JVM and running the tests on the main JVM ensuring you have sufficient memory or to pass args to increase the memory of the forked JVM

Check out the solution in this <a href="https://stackoverflow.com/a/49448372/5052928">answer</a>

blocks|key|1725491|text|对于我的例子，是我的代码调用System.exit(0)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1725492|以下是te文档中关于它的摘录：|1725493|1725494|+Surefire在任何时候都不支持调用System.exit()的测试或任何被引用的库。如果他们这样做，他们是不兼容的，你可能应该向库/供应商提交一个问题。|blockquote|1725495|1725496|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|M|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|N|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|J|$]]

For my case, it was my code calling System.exit(0).

Here is the extract about it from te documentation:

<blockquote>
 Surefire does not support tests or any referenced libraries calling System.exit() at any time. If they do so, they are incompatible with Surefire and you should probably file an issue with the library/vendor.
</blockquote>

blocks|key|1725505|text|我尝试了所有提供的解决方案(forking，systemloader，更多内存等)，都不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1725506|环境：构建在gitlab+ci环境中失败，在停靠容器中运行构建。|offset|length|style|BOLD|1725507|Solution：我们在2.20.1版本中使用了surefireplugin，升级到2.21.0或更高版本(我们使用2.22.1)解决了这个问题。|1725508|原因：SUREFIRE-1422+-+surefire使用ps命令，该命令在docker环境中不可用，并导致“崩溃”。此问题已在2.21.0或更高版本中修复。|CODE|1725509|感谢另一个问题的回答：https://stackoverflow.com/a/50568662/2970422|1725510|entityMap|0|LINK|mutability|MUTABLE|url|https://issues.apache.org/jira/browse/SUREFIRE-1422|1|https://stackoverflow.com/a/50568662/2970422^0|0|0|2|0|0|8|0|0|2|T|2|3|D|0|0|B|18|1|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@$D|13|E|14|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|15|8|@$D|16|E|17|F|G]|$D|18|E|19|F|L]]|9|@$D|1A|E|1B|1|1C]]|A|$]]|$1|M|3|N|5|6|7|1D|8|@]|9|@$D|1E|E|1F|1|1G]]|A|$]]|$1|O|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]|W|$5|R|S|T|A|$U|X]]]]

I tried all the provided solutions (forking, systemloader, more memory etc..), nothing worked.

Environment: The build failed in gitlab ci environment, running the build inside a docker container.

Solution:
We used surefireplugin in version 2.20.1 and upgrading to 2.21.0 or greater (we used 2.22.1) fixed the issue.

Cause:
<a href="https://issues.apache.org/jira/browse/SUREFIRE-1422" rel="nofollow noreferrer">SUREFIRE-1422</a> - surefire uses the command <code>ps</code>, which wasnt available in the docker environment and led to the "crash". This issue is fixed in 2.21.0 or greater. 

Thanks to this answer from another question: <a href="https://stackoverflow.com/a/50568662/2970422">https://stackoverflow.com/a/50568662/2970422</a>

blocks|key|1725519|text|当我在端口5005上远程调试Selenium测试代码时，我在MacOS上也遇到了这个问题。这个问题原来是由仍然运行的剩余的surefire-forked-JVM引起的。Eclipse+IDE终端的日志输出没有显示潜在的问题，即已经在使用的地址。只有当我在MacOS终端中运行与Eclipse实际尝试运行的命令相同的命令时，才会显示日志消息：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1725520|/bin/sh+-c+cd+/path/to/your/project/directory+&&+/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre/bin/java+-Xdebug+-Xnoagent+-Djava.compiler=NONE+-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005+-jar+/path/to/target/surefire/surefirebooter230340673926465933.jar+/path/to/target/surefire+2019-06-28T10-50-02_140-jvmRun1+surefire6455775580414993159tmp+surefire_02461993428448591420tmp|CODE|1725521|终止恶意JVM实例(在活动监视器中查找java进程名称)已修复此问题。顺便说一下，我运行的是surefire插件版本2.21.0，与open+JDK8+(v1.8.0_212)没有任何问题。请注意，所有路径都将特定于您的构建环境，可能还包括端口(address=5005)。|1725522|entityMap^0|3B|1F|0|0|BL|0|BL|0|0|3T|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|K|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|L|$]]

I ran into this issue as well on MacOS while remote debugging Selenium test code on port 5005. The problem turned out to be caused by a leftover surefire-forked-JVM that remained running. Log output to the Eclipse IDE terminal did not show the underlying issue which was Address already in use. The log message was only shown when I ran the same command in a MacOS terminal that Eclipse was actually trying to run:

<code>/bin/sh -c cd /path/to/your/project/directory &amp;&amp; /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre/bin/java -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005 -jar /path/to/target/surefire/surefirebooter230340673926465933.jar /path/to/target/surefire 2019-06-28T10-50-02_140-jvmRun1 surefire6455775580414993159tmp surefire_02461993428448591420tmp
</code>

Killing the rogue JVM instance (look for a java process name in Activity Monitor) fixed the issue. By the way I am running the surefire plugin version 2.21.0 with no issues with open jdk 8 (v1.8.0_212). Note that all paths will be specific to your build environment and possibly the port (address=5005).

blocks|key|1480931|text|在升级到java12后，我遇到了类似的问题，对我来说，解决方案是更新jacoco版本<jacoco.version>0.8.3</jacoco.version>。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1480932|entityMap^0|16|12|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I faced similar issue after upgrading to java 12, for me the solution was to update jacoco version <code>&lt;jacoco.version&gt;0.8.3&lt;/jacoco.version&gt;</code>

blocks|key|1725545|text|在我的例子中，通过设置MAVEN_OPTS来增加mem很有帮助：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1725546|set+MAVEN_OPTS=-Xmx1024m|code-block|syntax|javascript|1725547|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

In my case increasing mem by setting MAVEN_OPTS helped:

<pre><code>set MAVEN_OPTS=-Xmx1024m
</code></pre>

blocks|key|3835786|text|我遇到了与Chad's类似的情况，但找到了不同的答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3835787|根据the+plugin+docs，您不能在<argLine>中使用${...}，因为Maven会在surefire插件(或任何其他插件)之前获取它进行替换。|style|CODE|3835788|从2.17版开始，该插件支持使用@{...}+${...}+代替进行属性替换。|BOLD|3835789|例如，将这个替换为|3835790|<argLine>XX:MaxPermSize=1024m+${moreArgs}</argLine>|code-block|syntax|javascript|3835791|有了这个|3835792|<argLine>XX:MaxPermSize=1024m+@{moreArgs}</argLine>|3835793|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/38925634/|1|http://maven.apache.org/surefire/maven-surefire-plugin/faq.html#late-property-evaluation^0|5|6|0|0|M|9|Y|6|2|F|1|0|G|6|N|6|U|9|G|6|N|6|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@$A|16|B|17|1|18]]|C|$]]|$1|D|3|E|5|6|7|19|8|@$A|1A|B|1B|F|G]|$A|1C|B|1D|F|G]]|9|@$A|1E|B|1F|1|1G]]|C|$]]|$1|H|3|I|5|6|7|1H|8|@$A|1I|B|1J|F|J]|$A|1K|B|1L|F|J]|$A|1M|B|1N|F|J]|$A|1O|B|1P|F|G]|$A|1Q|B|1R|F|G]]|9|@]|C|$]]|$1|K|3|L|5|6|7|1S|8|@]|9|@]|C|$]]|$1|M|3|N|5|O|7|1T|8|@]|9|@]|C|$P|Q]]|$1|R|3|S|5|6|7|1U|8|@]|9|@]|C|$]]|$1|T|3|U|5|O|7|1V|8|@]|9|@]|C|$P|Q]]|$1|V|3|-4|5|6|7|1W|8|@]|9|@]|C|$]]]|W|$X|$5|Y|Z|10|C|$11|12]]|13|$5|Y|Z|10|C|$11|14]]]]

I had a situation similar to <a href="https://stackoverflow.com/a/38925634/">Chad's</a>, but found a different answer.

Per <a href="http://maven.apache.org/surefire/maven-surefire-plugin/faq.html#late-property-evaluation" rel="nofollow noreferrer">the plugin docs</a>, you can't use <code>${...}</code> in <code>&lt;argLine&gt;</code> because Maven will pick that up for replacement before the surefire plugin (or any other plugin) does.

Since version 2.17, the plugin supports <code>@{...}</code> instead of <code>${...}</code> for property replacement.

So for example, replace this

<pre><code>&lt;argLine&gt;XX:MaxPermSize=1024m ${moreArgs}&lt;/argLine&gt;
</code></pre>

with this

<pre><code>&lt;argLine&gt;XX:MaxPermSize=1024m @{moreArgs}&lt;/argLine&gt;
</code></pre>

blocks|key|1485189|text|版本2.22.2在派生JVM方面存在实际问题。使用2.20版-它就像一个护身符！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1485190|1485191|<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-surefire-plugin</artifactId>
<version>2.20</version>|code-block|syntax|javascript|1485192|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|K|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|L|8|@]|9|@]|A|$F|G]]|$1|H|3|-4|5|6|7|M|8|@]|9|@]|A|$]]]|I|$]]

version 2.22.2 has real problems with forked JVMs. 
Use version 2.20 - it works like a charm!

<hr>

<pre><code>&lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
&lt;version&gt;2.20&lt;/version&gt;
</code></pre>

blocks|key|5252979|text|我使用文件夹名称作为测试和演示，所以它给出了这个问题(VM在没有正确说再见的情况下终止。虚拟机崩溃或System.exit调用)，但当我给文件夹命名为test_demo时，它解决了这个问题。(这个问题存在于windows操作系统中，带有"&“符号。)|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|5252980|将"&“替换为"_”|5252981|此问题可能是由文件夹名称中的某些特殊符号或额外空格引起的。|5252982|entityMap^0|A|5|23|9|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

I was using folder name As test&amp;demo so it was giving this problem (VM terminated without saying properly goodbye. VM crash or System.exit called),but When i gave folder name as test_demo then it solved this issue.(this problem is there with windows OS with "&amp;" symbol.)

Replace "&amp;" to "_"

This problem may cause with some special symbol or extra space in folder name.

blocks|key|3835829|text|我在使用maven+test运行单元测试时也遇到了同样的问题。尝试更改surefire版本，但它不起作用。最终解决方法如下:之前：(当问题发生时)：javac来自jdk+1.8+java指向jdk+1.11的java+bin当前：(当问题得到解决时)：javac和java都指向jdk+1.8的bin|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3835830|问候Teja。|3835831|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I was facing the same issue when running unit tests using maven test .
Tried changing the surefire versions but it dinnt work. 
Finally managed to solve as follows:
EARLIER: (when the issue was happening):
 javac is from jdk 1.8
 java was pointing to the java bin from jdk 1.11
CURRENT: (when the issue got resolved):
 both javac &amp; java are pointing to the bins from jdk 1.8

Regards
Teja .

blocks|key|3835833|text|我将surefire插件更新为以下内容，这解决了我的问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3835834|+++++++++++<plugin>
++++++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++++++<artifactId>maven-surefire-plugin</artifactId>
++++++++++++++++<version>2.22.2</version>
++++++++++++++++<configuration>
++++++++++++++++++++<argLine>-Xmx1024m+-XX:MaxPermSize=256m</argLine>
++++++++++++++++++++<forkCount>1</forkCount>
++++++++++++++++++++<reuseForks>true</reuseForks>
++++++++++++++++++++<runOrder>alphabetical</runOrder>
++++++++++++++++</configuration>
++++++++++++</plugin>|code-block|syntax|javascript|3835835|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I updated the surefire plugin to the following and this solved my problem:
<pre><code> &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.22.2&lt;/version&gt;
 &lt;configuration&gt;
 &lt;argLine&gt;-Xmx1024m -XX:MaxPermSize=256m&lt;/argLine&gt;
 &lt;forkCount&gt;1&lt;/forkCount&gt;
 &lt;reuseForks&gt;true&lt;/reuseForks&gt;
 &lt;runOrder&gt;alphabetical&lt;/runOrder&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
</code></pre>

blocks|key|3835837|text|这似乎是某些Windows计算机上的线程同步问题。如果您在Windows上遇到此问题，请尝试将输出重定向到一个文件：mvn+clean+install+>+output.txt|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3835838|entityMap^0|1M|U|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

This seems to be a thread sync issue on certain Windows machines. If you're having this problem with Windows, try redirecting the output to a file: <code>mvn clean install &gt; output.txt</code>

blocks|key|1726068|text|我在一个运行测试的应用程序中遇到了同样的问题，该应用程序在运行测试时将大量XML记录到控制台。我认为这个问题与测试分支将其控制台日志发送到主maven线程以输出到屏幕的方式有关。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1726069|我在我的测试logback文件中将违规类的日志设置为WARN，从而解决了这个问题。|1726070|例如logback-test.xml|1726071|<configuration+debug="true">
++<include+resource="org/springframework/boot/logging/logback/defaults.xml"+/>
++<include+resource="org/springframework/boot/logging/logback/console-appender.xml"+/>

++<logger+name="com.foo.ClassWithLotsOfXmlLogging"+level="WARN"+/>

++<root+level="INFO">
++++<appender-ref+ref="CONSOLE"/>
++</root>
</configuration>|code-block|syntax|javascript|1726072|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|P|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I had the same problem in an app that was logging lots of XML to the console whilst it was running tests. I think the issue is something to do with the way the test fork sends its console logging to the main maven thread to be output to the screen.
I worked around the issue by setting the logging of the offending class to WARN in my test logback file.
Eg logback-test.xml
<pre class="lang-xml prettyprint-override"><code>&lt;configuration debug=&quot;true&quot;&gt;
 &lt;include resource=&quot;org/springframework/boot/logging/logback/defaults.xml&quot; /&gt;
 &lt;include resource=&quot;org/springframework/boot/logging/logback/console-appender.xml&quot; /&gt;

 &lt;logger name=&quot;com.foo.ClassWithLotsOfXmlLogging&quot; level=&quot;WARN&quot; /&gt;

 &lt;root level=&quot;INFO&quot;&gt;
 &lt;appender-ref ref=&quot;CONSOLE&quot;/&gt;
 &lt;/root&gt;
&lt;/configuration&gt;
</code></pre>

blocks|key|1726074|text|我在Java8和spring+boot+5.2.7上也遇到了同样的问题(包括插件，开箱即用)。插件的版本是默认的(2.22.2)。在我的例子中，问题只发生在团队中的一些机器上，而在其他机器上一切正常。我猜这与maven检测到的内核数量有关。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1726075|我用以下设置修复了它：|1726076|++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-surefire-plugin</artifactId>
++++++++++++<configuration>
++++++++++++++++<reuseForks>false</reuseForks>
++++++++++++</configuration>
++++++++</plugin>|code-block|syntax|javascript|1726077|我尝试了许多建议的方法，但在我的情况下都不起作用。|1726078|这种解决方案唯一的缺点是禁用了fork的重用，现在测试运行速度变慢了。|1726079|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I had the same problem with Java 8 and spring boot 5.2.7 (plugin is included, out of the box). The version of the plugin is default (2.22.2). In my case the problems was happening only on some machines in team, while on the other machines everything was fine. I guess it have something to do with the number of cores maven detected.
I fixed it with these settings:
<pre><code> &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;reuseForks&gt;false&lt;/reuseForks&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
</code></pre>
I have tried many of the proposed approaches, but nothing was working in my case.
The only downside with this solution is disabling forks' reuse and tests are running slower now.

blocks|key|1485212|text|添加配置文件后，我能够删除此错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1485213|<profile>
++++++++++++<id>surefire-windows-fork-disable</id>
++++++++++++<activation>
++++++++++++++++<os>
++++++++++++++++++++<family>Windows</family>
++++++++++++++++</os>
++++++++++++</activation>
++++++++++++<build>
++++++++++++++++<pluginManagement>
++++++++++++++++++++<plugins>
++++++++++++++++++++++++<plugin>
++++++++++++++++++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++++++++++++++++++<artifactId>maven-surefire-plugin</artifactId>
++++++++++++++++++++++++++++<configuration>
++++++++++++++++++++++++++++++++<forkCount>0</forkCount>
++++++++++++++++++++++++++++++++<useSystemClassLoader>false</useSystemClassLoader>
++++++++++++++++++++++++++++</configuration>
++++++++++++++++++++++++</plugin>
++++++++++++++++++++</plugins>
++++++++++++++++</pluginManagement>
++++++++++++</build>
++++++++</profile>|code-block|syntax|javascript|1485214|似乎这是一个关于maven+surefire+forks的windows问题。|1485215|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

this error I was able to remove after adding profile:
<pre><code>&lt;profile&gt;
 &lt;id&gt;surefire-windows-fork-disable&lt;/id&gt;
 &lt;activation&gt;
 &lt;os&gt;
 &lt;family&gt;Windows&lt;/family&gt;
 &lt;/os&gt;
 &lt;/activation&gt;
 &lt;build&gt;
 &lt;pluginManagement&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;forkCount&gt;0&lt;/forkCount&gt;
 &lt;useSystemClassLoader&gt;false&lt;/useSystemClassLoader&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
 &lt;/pluginManagement&gt;
 &lt;/build&gt;
 &lt;/profile&gt;
</code></pre>
seems that this is a windows problem regarding maven surefire forks

blocks|key|5253005|text|我花了这么多时间，对我来说，这几乎总是与"console“相关，与实际的forking无关。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|5253006|简而言之，我的解决方案是：|5253007|5253008|添加-B+(批处理模式)|unordered-list-item|CODE|5253009|添加JVM参数-Djansi.force=true+-Djansi.passthrough=true|5253010|5253011|在一个给定的项目上，这将在一个新的windows控制台(cmd.exe)中系统地失败|5253012|path_to_maven\boot\plexus-classworlds-2.6.0.jar+org.codehaus.plexus.classworlds.launcher.Launcher+-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.|5253013|=UTF-8+-Djansi.force=true+-Djansi.passthrough=true+-classpath+-B+clean+install+-B|blockquote|5253014|5253015|5253016|这将在一个新的控制台窗口(cmd.exe)中始终工作。|5253017|path_to_maven\boot\plexus-classworlds-2.6.0.jar+org.codehaus.plexus.classworlds.launcher.Launcher+-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.|5253018|=UTF-8+-Djansi.force=true+-Djansi.passthrough=true+-classpath+-B+clean+install+-B|5253019|5253020|5253021|注意，这两个命令都有-B+(应该关闭着色的批处理模式)，唯一的区别是|5253022|-Djansi.force=true+-Djansi.passthrough=true|code-block|syntax|javascript|5253023|现在我只需要传递这些"JVM“和"mvn.cmd”就可以让它变得更好。|5253024|我猜是这样的：Is+there+a+way+to+pass+jvm+args+via+command+line+to+maven?|5253025|5253026|下面是一些背景知识：|5253027|自从maven的最新版本(3.x+%2B)以来，我反复遇到这个问题。我在这里尝试了许多解决方案，有时是幸运的，有时不是。|5253028|这篇来自官方文档的文章一直都是无用的：https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html|5253029|但是有一些常量，当我遇到这个问题时：|5253030|5253031|Always+on+windows，project|5253032|Jenkins大量控制台输出。在*IT+|5253033|(故障安全集成测试)|5253034|中，并非所有在给定版本上遇到错误的团队的开发人员都能通过|5253035|大量控制台输出|5253036|5253037|关键的发现是，我注意到在Eclipse中，一个完整的maven构建(干净安装)可以工作(不管有没有嵌入式maven版本)。|5253038|所以我弄清楚了Eclipse使用的是哪个命令(感谢：How+do+I+get+the+command-line+for+an+Eclipse+run+configuration?)|5253039|从那里，我能够确定解决方案是。|5253040|在人们说的地方看到其他答案|5253041|到logfile|5253042|reduce日志level|5253043|
|5253044|https://stackoverflow.com/a/52033799/1634131|5253045|5253046|https://stackoverflow.com/a/64132709/1634131|5253047|5253048|etc|5253049|
的|5253050|输出|5253051|5253052|很明显这里面有个bug。在Maven中，或者在windows控制台中，或者在Jansi库中，或者在这些组件的集成中。|5253053|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/12525288/is-there-a-way-to-pass-jvm-args-via-command-line-to-maven|1|https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html|2|https://stackoverflow.com/questions/20891108/how-do-i-get-the-command-line-for-an-eclipse-run-configuration|3|4^0|L|7|0|0|0|2|2|0|7|17|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|7|1M|0|0|0|0|0|J|2B|1|0|0|0|0|0|0|0|0|0|0|Q|1R|2|0|0|0|0|0|0|0|18|3|0|0|0|18|4|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|39|8|@$9|3A|A|3B|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|3C|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|3D|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|3E|8|@$9|3F|A|3G|B|L]]|D|@]|E|$]]|$1|M|3|N|5|K|7|3H|8|@$9|3I|A|3J|B|L]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|3K|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|3L|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|3M|8|@]|D|@]|E|$]]|$1|T|3|U|5|V|7|3N|8|@]|D|@]|E|$]]|$1|W|3|-4|5|6|7|3O|8|@]|D|@]|E|$]]|$1|X|3|-4|5|6|7|3P|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|3Q|8|@]|D|@]|E|$]]|$1|10|3|11|5|6|7|3R|8|@]|D|@]|E|$]]|$1|12|3|13|5|V|7|3S|8|@]|D|@]|E|$]]|$1|14|3|-4|5|6|7|3T|8|@]|D|@]|E|$]]|$1|15|3|-4|5|6|7|3U|8|@]|D|@]|E|$]]|$1|16|3|17|5|6|7|3V|8|@]|D|@]|E|$]]|$1|18|3|19|5|1A|7|3W|8|@]|D|@]|E|$1B|1C]]|$1|1D|3|1E|5|6|7|3X|8|@]|D|@]|E|$]]|$1|1F|3|1G|5|6|7|3Y|8|@]|D|@$9|3Z|A|40|1|41]]|E|$]]|$1|1H|3|-4|5|6|7|42|8|@]|D|@]|E|$]]|$1|1I|3|1J|5|6|7|43|8|@]|D|@]|E|$]]|$1|1K|3|1L|5|6|7|44|8|@]|D|@]|E|$]]|$1|1M|3|1N|5|6|7|45|8|@]|D|@$9|46|A|47|1|48]]|E|$]]|$1|1O|3|1P|5|6|7|49|8|@]|D|@]|E|$]]|$1|1Q|3|-4|5|6|7|4A|8|@]|D|@]|E|$]]|$1|1R|3|1S|5|K|7|4B|8|@]|D|@]|E|$]]|$1|1T|3|1U|5|K|7|4C|8|@]|D|@]|E|$]]|$1|1V|3|1W|5|K|7|4D|8|@]|D|@]|E|$]]|$1|1X|3|1Y|5|6|7|4E|8|@]|D|@]|E|$]]|$1|1Z|3|20|5|K|7|4F|8|@]|D|@]|E|$]]|$1|21|3|-4|5|6|7|4G|8|@]|D|@]|E|$]]|$1|22|3|23|5|6|7|4H|8|@]|D|@]|E|$]]|$1|24|3|25|5|6|7|4I|8|@]|D|@$9|4J|A|4K|1|4L]]|E|$]]|$1|26|3|27|5|6|7|4M|8|@]|D|@]|E|$]]|$1|28|3|29|5|6|7|4N|8|@]|D|@]|E|$]]|$1|2A|3|2B|5|6|7|4O|8|@]|D|@]|E|$]]|$1|2C|3|2D|5|K|7|4P|8|@]|D|@]|E|$]]|$1|2E|3|2F|5|6|7|4Q|8|@]|D|@]|E|$]]|$1|2G|3|2H|5|K|7|4R|8|@]|D|@$9|4S|A|4T|1|4U]]|E|$]]|$1|2I|3|2F|5|6|7|4V|8|@]|D|@]|E|$]]|$1|2J|3|2K|5|K|7|4W|8|@]|D|@$9|4X|A|4Y|1|4Z]]|E|$]]|$1|2L|3|2F|5|6|7|50|8|@]|D|@]|E|$]]|$1|2M|3|2N|5|K|7|51|8|@]|D|@]|E|$]]|$1|2O|3|2P|5|6|7|52|8|@]|D|@]|E|$]]|$1|2Q|3|2R|5|K|7|53|8|@]|D|@]|E|$]]|$1|2S|3|-4|5|6|7|54|8|@]|D|@]|E|$]]|$1|2T|3|2U|5|6|7|55|8|@]|D|@]|E|$]]|$1|2V|3|-4|5|6|7|56|8|@]|D|@]|E|$]]]|2W|$2X|$5|2Y|2Z|30|E|$31|32]]|33|$5|2Y|2Z|30|E|$31|34]]|35|$5|2Y|2Z|30|E|$31|36]]|37|$5|2Y|2Z|30|E|$31|2H]]|38|$5|2Y|2Z|30|E|$31|2K]]]]

I had this many time, and for me, this is almost always &quot;console&quot; related and has nothing to do with actual forking.
In short, my solution is :
<ul>
<li>Add <code>-B</code> (batch mode)</li>
<li>Add JVM args <code>-Djansi.force=true -Djansi.passthrough=true</code></li>
</ul>
On a given project this would fails systematically in a new windows console (cmd.exe)
<blockquote>
[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
</blockquote>
This will always works in a new console window (cmd.exe).
<blockquote>
[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
</blockquote>
Notice that both command have -B (batch mode which should turn off coloring), and the only difference is
<pre><code>-Djansi.force=true -Djansi.passthrough=true
</code></pre>
Now I just need to be able to pass these &quot;JVM args&quot; the the &quot;mvn.cmd&quot; to make this better.
Something like this I guess : <a href="https://stackoverflow.com/questions/12525288/is-there-a-way-to-pass-jvm-args-via-command-line-to-maven">Is there a way to pass jvm args via command line to maven?</a>
<hr />
A bit of background :
I had this problem repeatedly since the latest versions of maven (3.x +).
I have tried many of the solutions here, sometimes with luck, sometimes not.
This article from the official doc has always been useless : <a href="https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html" rel="nofollow noreferrer">https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html</a>
But there are constants, when I ran in this problem :
<ul>
<li>Always on windows, locally</li>
<li>Always LOTS of console output.</li>
<li>Not all dev of the team getting the error on a given project</li>
<li>Jenkins build would pass</li>
<li>LOTS of console output in *IT test (failsafe integration tests)</li>
</ul>
The key discovery was that I noticed that within Eclipse, (with or without the embedded maven version) a ful maven build (clean install) would work.
So I figured out which command Eclipse was using (thanks : <a href="https://stackoverflow.com/questions/20891108/how-do-i-get-the-command-line-for-an-eclipse-run-configuration">How do I get the command-line for an Eclipse run configuration?</a>)
From there, I was able to determine was the solution was.
See other answer where people are saying
<ul>
<li>output to logfile</li>
<li>reduce log level</li>
<li><a href="https://stackoverflow.com/a/52033799/1634131">https://stackoverflow.com/a/52033799/1634131</a></li>
<li><a href="https://stackoverflow.com/a/64132709/1634131">https://stackoverflow.com/a/64132709/1634131</a></li>
<li>etc</li>
</ul>
There is clearly a bug there. Either in Maven or in the windows console, or in the Jansi lib, or in the integration of these components.

blocks|key|1480962|text|简单的解决方案:应该添加src/test/resources/logback.xml|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1480963|<configuration+debug="false">
<appender+name="STDOUT"+class="ch.qos.logback.core.ConsoleAppender">
++++<encoder>
++++++++<pattern>%25date{HH:mm:ss.SSS}+%25highlight(%25-5level)
++++++++++++%25gray(%25logger{90})+%25X{X-ApplicationId}+%25msg%25n
++++++++</pattern>
++++</encoder>
</appender>|code-block|syntax|javascript|1480964|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Simple solution:
You should add src/test/resources/logback.xml
<pre><code>&lt;configuration debug=&quot;false&quot;&gt;
&lt;appender name=&quot;STDOUT&quot; class=&quot;ch.qos.logback.core.ConsoleAppender&quot;&gt;
 &lt;encoder&gt;
 &lt;pattern&gt;%date{HH:mm:ss.SSS} %highlight(%-5level)
 %gray(%logger{90}) %X{X-ApplicationId} %msg%n
 &lt;/pattern&gt;
 &lt;/encoder&gt;
&lt;/appender&gt;
</code></pre>

blocks|key|5253055|text|我最近在一个由JHipster+6.10.5使用spring-boot+2.2.7.RELEASE和maven+surefire插件3.0.0-M4生成的应用程序中遇到了同样的问题。这是由于测试日志过长而导致的超时。在pom.xml+(pluginManagement下)的maven-surefire-plugin中添加如下配置参数即可解决：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5253056|1200|5253057|请参阅https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkedProcessExitTimeoutInSeconds|offset|length|5253058|entityMap|0|LINK|mutability|MUTABLE|url|https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkedProcessExitTimeoutInSeconds^0|0|0|3|2W|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I recently had the same problem in an application generated by JHipster 6.10.5 using spring-boot 2.2.7.RELEASE and maven surefire plugin 3.0.0-M4 . It was caused by a timeout due to the extremely long testing log. It was solved by adding the following configuration parameter to maven-surefire-plugin in pom.xml (under pluginManagement):
&lt;forkedProcessExitTimeoutInSeconds&gt;1200&lt;/forkedProcessExitTimeoutInSeconds&gt;
See <a href="https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkedProcessExitTimeoutInSeconds" rel="nofollow noreferrer">https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkedProcessExitTimeoutInSeconds</a>

blocks|key|5253060|text|我的场景是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5253061|5253062|我的测试有很多日志输出(我的意思是a+lot+!)|unordered-list-item|offset|length|style|BOLD|5253063|Surefire插件v2.22.2|5253064|错误只发生在集成开发环境内部，如果从命令行执行mvn命令则不会。<代码>H29<代码>H110没有任何来自Surefire插件的D11文件或传统的来自Java二进制文件的崩溃文件。<代码>H213<代码>F214|CODE|5253065|5253066|对我来说，有两件事一直是解决方案(它们是替代方案)：|5253067|forking+Do+not+use+forking:+set+Surefire+plugin+property+forkcount+=+0.|5253068|increase+|5253069|+property+forkedProcessExitTimeoutInSeconds从30秒设置为300秒。plugin+documentation指出，如果达到此超时时间，您将看到错误消息There+was+a+timeout+in+the+fork。我没有看到这样的错误消息，但是它一直在修复这个问题，以增加这个超时值。|ordered-list-item|5253070|5253071|5253072|您可能希望使用解决方案(2)，因为派生是可取的。|5253073|为什么？|5253074|我的理论是，如果有很多日志输出，那么在fork关闭时仍然需要进行很多处理(特别是如果你在IDE中运行，该IDE捕获输出，并可能使用内存映射文件作为其窗口内容)。简而言之:在测试结束时，仍有许多文本等待转发到IDE中。看起来30秒还不够。|5253075|这也解释了为什么一些开发人员会看到这个问题，而另一些人不会。在测试完成时还剩下多少输出处理可能是cpu功率、磁盘速度等的函数。|5253076|如果我是对的-无法证明这一点-那么所有的建议，如重定向日志输出和降低日志级别，都是针对症状，而不是原因。|5253077|entityMap|0|LINK|mutability|MUTABLE|url|http://maven.apache.org/surefire/maven-surefire-plugin/examples/shutdown.html^0|0|0|H|5|0|0|N|3|0|0|0|1L|D|0|0|A|X|2O|V|1J|K|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1K|8|@$F|1L|G|1M|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|1N|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|1O|8|@$F|1P|G|1Q|H|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1S|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1T|8|@$F|1U|G|1V|H|N]]|9|@]|A|$]]|$1|T|3|U|5|E|7|1W|8|@]|9|@]|A|$]]|$1|V|3|W|5|X|7|1X|8|@$F|1Y|G|1Z|H|N]|$F|20|G|21|H|N]]|9|@$F|22|G|23|1|24]]|A|$]]|$1|Y|3|-4|5|6|7|25|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|26|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|27|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|28|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|29|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|2A|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|2B|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]]|1B|$1C|$5|1D|1E|1F|A|$1G|1H]]]]

My scenario is
<ul>
<li>My test has lots of log output (and I mean a lot !)</li>
<li>Surefire plugin v2.22.2</li>
<li>The error only happens from inside the IDE, not if the <code>mvn</code> command is executed from a command line.</li>
<li>no sign of any <code>.dump</code> file from Surefire plugin or traditional <code>hs_err</code> crash files from Java binary.</li>
</ul>
Two things consistently worked as solutions for me (they are alternatives):
<ol>
<li>Do not use forking: set Surefire plugin property <code>forkcount = 0</code>.</li>
<li>increase Surefire plugin property
<code>forkedProcessExitTimeoutInSeconds</code> from 30 secs to say 300 secs. The <a href="http://maven.apache.org/surefire/maven-surefire-plugin/examples/shutdown.html" rel="nofollow noreferrer">plugin documentation</a> says that if this timeout is hit you'll see error message <code>There was a timeout in the fork</code>. I saw no such error message, yet it consistently fixes the problem to increase this timeout value.</li>
</ol>
You would probably want to use solution (2) as forking is desirable.
<h3>Why?</h3>
My theory is that if lots of log output then there's still lots of processing that needs to be done on fork shutdown (in particular if you are running inside an IDE which captures the output and possibly uses a memory mapped files for its window content). In short: at the time the test is finished there's still a lot of text waiting to be forwarded into your IDE. It seems 30s simply isn't enough for this.
This also explains why some devs will see the problem, while others not. How much output processing is left to do at the time of test finish is probably a function of cpu power, disk speed, etc.
If I'm right in this - cannot prove it - then all suggestions like redirecting the log output and decreasing the logging level are IMO treating the symptom, not the cause.

blocks|key|3835874|text|发生在我身上:如果您的项目依赖于docker机器或/和数据库来成功构建，那么请首先检查您的db实例是否已启动，您的docker是否也已启动，因为可能有一些单元测试在后台运行……检查一下，特别是在启动笔记本电脑之后..希望这能帮助到一些人|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3835875|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Happened to me: if your project depends on docker machine or/ and database to build successfully then please check first that your db instance is up and your docker is also up because maybe there are some unit tests running in the background ... check that especially after starting your laptop.. hope that could help someone

blocks|key|3835877|text|你可以使用下面的命令。因为您的单元测试需要派生。关于你在单元测试中使用线程问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3835878|mvn+test+-DforkCount=2|code-block|syntax|javascript|3835879|我希望如此。这很有帮助。|3835880|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

you can use below command. Because your unit tests need to fork. That problem about you use thread in your unit test.
<pre><code>mvn test -DforkCount=2
</code></pre>
I hope. Its helpful.

blocks|key|1726138|text|我的解决方案是更改90+to+120.中的Jenkinsfile中提到的超时|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|1726139|pipeline+{
++++agent+{+label+projectName+}

options+{
++++disableConcurrentBuilds()
++++buildDiscarder(logRotator(numToKeepStr:'5'))
++++timeout(time:+90,+unit:+'MINUTES')
}|code-block|syntax|javascript|1726140|谢谢，SA|1726141|entityMap^0|9|A|L|B|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|U|8|@]|E|@]|F|$J|K]]|$1|L|3|M|5|6|7|V|8|@]|E|@]|F|$]]|$1|N|3|-4|5|6|7|W|8|@]|E|@]|F|$]]]|O|$]]

my resolution was to change the timeout mentioned in Jenkinsfile from <code>90 to 120.</code>
<pre><code>pipeline {
 agent { label projectName }

options {
 disableConcurrentBuilds()
 buildDiscarder(logRotator(numToKeepStr:'5'))
 timeout(time: 90, unit: 'MINUTES')
}
</code></pre>
Thanks,
SA

blocks|key|1726143|text|这对我很有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1726144|<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.0.0-M5</version>
<configuration>
++++<argLine>-Dfile.encoding=UTF-8</argLine>
</configuration>
</plugin>|code-block|syntax|javascript|1726145|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This worked for me.
<pre class="lang-html prettyprint-override"><code>&lt;plugin&gt;
&lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
&lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
&lt;version&gt;3.0.0-M5&lt;/version&gt;
&lt;configuration&gt;
 &lt;argLine&gt;-Dfile.encoding=UTF-8&lt;/argLine&gt;
&lt;/configuration&gt;
&lt;/plugin&gt;
</code></pre>

blocks|key|1480980|text|适用于我的解决方案set：<forkCount>0</forkCount>|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1480981|即|1480982|<plugin>
++<groupId>org.apache.maven.plugins</groupId>
++<artifactId>maven-surefire-plugin</artifactId>
++<configuration>
++++<forkCount>0</forkCount>+
++++<argLine>-Xmx1024m+-XX:MaxPermSize=256m</argLine>
++</configuration>
</plugin>|code-block|syntax|javascript|1480983|entityMap^0|D|O|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Solution that worked for me, set: <code>&lt;forkCount&gt;0&lt;/forkCount&gt;</code>
i.e.
<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;forkCount&gt;0&lt;/forkCount&gt; 
 &lt;argLine&gt;-Xmx1024m -XX:MaxPermSize=256m&lt;/argLine&gt;
 &lt;/configuration&gt;
&lt;/plugin&gt;
</code></pre>

blocks|key|5253093|text|在将Maven从2.6.3更新到2.8.4之后，我也遇到了同样的问题。问题是forked+JVM内存不足，所以只需在Surefire插件配置中将内存从1024Mb增加到2048Mb，就解决了这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5253094|++++++++<plugin>
++++++++++++<artifactId>maven-surefire-plugin</artifactId>
++++++++++++<configuration>
++++++++++++++++
++++++++++++++++<argLine>${argLine}+-Dfile.encoding=UTF-8+-Xmx2048m</argLine>
++++++++++++</configuration>
++++++++</plugin>|code-block|syntax|javascript|5253095|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I had the same problem while after updating Maven from 2.6.3 to 2.8.4. The problem was that forked JVM crushed by out of memory, so just increased memory from 1024Mb to 2048Mb in Surefire plugin config and that solved the issue
<pre><code> &lt;plugin&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;!--suppress UnresolvedMavenProperty --&gt;
 &lt;argLine&gt;${argLine} -Dfile.encoding=UTF-8 -Xmx2048m&lt;/argLine&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
</code></pre>

Please help me to solve this issue. I do not exactly understand what the error in the log means.

<pre><code>[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 21.749s
[INFO] Finished at: Thu Apr 24 10:10:20 IST 2014
[INFO] Final Memory: 15M/37M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.15:test (default-test) on project samples.simpleforwarding: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.15:test failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ?
[ERROR] Command wascmd.exe /X /C ""C:\Program Files\Java\jdk1.7.0_55\jre\bin\java" -Xmx1024m -XX:MaxPermSize=256m -jar E:\OpenDayLight\controller\opendaylight\samples\simpleforwarding\target\surefire\surefirebooter53410321571238933.jar E:\OpenDayLight\controller\opendaylight\samples\simpleforwarding\target\surefire\surefire86076271125218001tmp E:\OpenDayLight\controller\opendaylight\samples\simpleforwarding\target\surefire\surefire_01846991116135903536tmp"
[ERROR] -&gt; [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
</code></pre>

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

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

请帮我解决这个问题。我不完全理解日志中的错误是什么意思。[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] --------------------------...

问派生的VM在没有正确说再见的情况下终止。虚拟机崩溃或System.exit被调用
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问派生的VM在没有正确说再见的情况下终止。虚拟机崩溃或System.exit被调用EN