[
https://issues.apache.org/jira/browse/SUREFIRE-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987805#comment-14987805
]
Ralph Goers edited comment on SUREFIRE-1193 at 11/3/15 6:37 PM:
----------------------------------------------------------------
Yeah, I don't have the Jenkins info in front of me. But when I ran the build on
my MacBook Pro I was getting hangs - sometimes in log4j-api and sometimes in
log4j-iostreams. It wasn't consistent. With the older versions of the surefire
plugin we have never experienced this. I should note that on the Mac Maven just
completely hangs - I don't see the failure that happens in Jenkins. I can't
even get a thread dump with jstack.
Gary - do you know why he is getting those failures in log4j-core? We have one
or two tests that seem to periodically fail in Jenkins - but they never fail on
my Mac. However, I've never seen those two particular tests fail.
was (Author: [email protected]):
Yeah, I don't have the Jenkins info in front of me. But when I ran the build on
my MacBook Pro I was getting hangs - sometimes in log4j-api and sometimes in
log4j-iostreams. It wasn't consistent. With the older versions of the surefire
plugin we have never experienced this.
Gary - do you know why he is getting those failures in log4j-core? We have one
or two tests that seem to periodically fail in Jenkins - but they never fail on
my Mac. However, I've never seen those two particular tests fail.
> 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
> Assignee: Tibor Digana
> 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)
