You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by ma...@apache.org on 2022/01/29 20:42:53 UTC
[logging-log4j2] branch master updated: Use forked parallel tests instead of concurrent
This is an automated email from the ASF dual-hosted git repository.
mattsicker pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
The following commit(s) were added to refs/heads/master by this push:
new 3bb4245 Use forked parallel tests instead of concurrent
3bb4245 is described below
commit 3bb424533059c19c363c1382a9c99da389059cf1
Author: Matt Sicker <ma...@apache.org>
AuthorDate: Sat Jan 29 14:42:43 2022 -0600
Use forked parallel tests instead of concurrent
It seems as though there are some API tests that rely on some sort of shared state that can't be reproducibly tested with in-process concurrent tests compared to forking.
Signed-off-by: Matt Sicker <ma...@apache.org>
---
log4j-api-test/pom.xml | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/log4j-api-test/pom.xml b/log4j-api-test/pom.xml
index b9c53a3..7b3d2f1 100644
--- a/log4j-api-test/pom.xml
+++ b/log4j-api-test/pom.xml
@@ -159,7 +159,7 @@
<configurationParameters>
<!-- LOG4J2-2921: use parallel test execution by default -->
junit.jupiter.execution.parallel.enabled = true
- junit.jupiter.execution.parallel.mode.default = concurrent
+ junit.jupiter.execution.parallel.mode.default = fork
</configurationParameters>
</properties>
<forkCount>1C</forkCount>
@@ -249,10 +249,9 @@
project -->
<failOnError>false</failOnError>
<detectOfflineLinks>false</detectOfflineLinks>
- <additionalparam>-Xdoclint:none</additionalparam>
<linksource>true</linksource>
<links>
- <link>http://www.osgi.org/javadoc/r4v43/core/</link>
+ <link>https://www.osgi.org/javadoc/r4v43/core/</link>
</links>
<source>8</source>
</configuration>