[
https://issues.apache.org/jira/browse/SUREFIRE-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14988209#comment-14988209
]
Tibor Digana edited comment on SUREFIRE-1193 at 11/3/15 9:51 PM:
-----------------------------------------------------------------
[~ralph.go...@dslextreme.com]
Why the Jenkins build crashed after hanging? It really hanged for some time so
that the CPU was very low?
Who did shutdown the forked JVM?
Can you just print test class name in @BeforeClass?
We need to see which class is in the middle.
There's one situation when the JVM may shutdown itself. The plugin JVM sends
commands to forked JVM. The Forked JVM receives the command in std/in. If the
std/in stream is corrupted so that the command cannot be decoded, the reader
throws an exception which may result shutdown. We should find out if this is
happening. If it is this case then the question is why Maven process would
corrupt the stream.
was (Author: tibor17):
[~ralph.go...@dslextreme.com]
Why the Jenkins build crashed after hanging? It really hanged for some time so
that the CPU was very low?
Who did shutdown the forked JVM?
Can you just print test class name in @BeforeClass?
We need to see which clas is in the middle.
There's one situation when the JVM may shutdown itself. The plugin JVM sends
commands to forked JVM. The Forked JVM receives the command in std/in. If the
std/in stream is corrupted so that the command cannot be decoded, the reader
throws an exception which may result shutdown. We should find out if this is
happening. If it is this case then the question is why Maven process would
corrupt the stream.
> 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)
