[
https://issues.apache.org/jira/browse/SUREFIRE-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987242#comment-14987242
]
Tibor Digana commented on SUREFIRE-1193:
----------------------------------------
[~garydgregory]
I have run mvn test on project [1] with latest commit [2] and nothing hangs in
Log4j API.
I did change surefire and failsafe version from 2.18.1 to 2.19 in the first POM.
[INFO] Apache Log4j 2 .................................... SUCCESS [ 10.075 s]
[INFO] Apache Log4j API .................................. SUCCESS [ 39.760 s]
[INFO] Apache Log4j Core ................................. FAILURE [09:50 min]
Tests in error:
SslConfigurationTest.connectionFailsWithoutValidServerCertificate:53 » Connect
SslConfigurationTest.emptyConfigurationHasDefaultTrustStore:43 » Connect
Conne...
Tests run: 949, Failures: 0, Errors: 2, Skipped: 31
Do you have Jenkins CI timeout setup to [ 50.035 s] ?
[1] https://github.com/apache/logging-log4j2
[2] commit 71c863dd52110766b6aadf3aaeb72f4607a3caf2
I am using Win7. Can you check it out with Windows?
Is any test platform dependent?
> Surefire 2.19 hangs in the log4j build
> --------------------------------------
>
> Key: SUREFIRE-1193
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1193
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.19
> Reporter: Ralph Goers
> Attachments: SUREFIRE-1193.console.txt
>
>
> Log4j is getting periodic failures in Jenkins with the messages shown below.
> I am also seeing running the tests hang in various log4j modules when
> building on my MacBook Pro. The build never hung when using 2.18. We have
> reverted back to surefire 2.18 due to this.
> The full build output is temporarily available at
> https://builds.apache.org/job/Log4j%202.x/1520/console. We only keep the last
> 15 builds.
> ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19:test (default-test) on
> project log4j-api: ExecutionException The forked VM terminated without
> properly saying goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd
> "<https://builds.apache.org/job/Log4j%202.x/ws/log4j-api";> &&
> /home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk-1.7u51/jre/bin/java
> -XX:MaxPermSize=512m -jar
> '<https://builds.apache.org/job/Log4j%202.x/ws/log4j-api/target/surefire/surefirebooter7073284324062596703.jar'>
>
> '<https://builds.apache.org/job/Log4j%202.x/ws/log4j-api/target/surefire/surefire9073033079471575703tmp'>
>
> '<https://builds.apache.org/job/Log4j%202.x/ws/log4j-api/target/surefire/surefire_84682619741166881372tmp'>
> [ERROR] -> [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/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :log4j-api
> [JENKINS] Archiving <https://builds.apache.org/job/Log4j%202.x/ws/l
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
