[
https://issues.apache.org/jira/browse/SUREFIRE-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992145#comment-14992145
]
Tibor Digana commented on SUREFIRE-1193:
----------------------------------------
I would say both 23056 and 23045 were triggered by master 23031.
Can you find out if all tests were finished and find the number of completed
tests? Please see the reports in target/surefire-reports. Count them and
compare with expected count.
If the test set was completed, then only non-daemon thread may hold on VM. But
this VM cannot exit normally while using non-daemon Threads in tests and
therefore it times out after 30 sec and kills itself (this operation only on
after all tests completed).
Is it this case?
AFAIK shutdown hook in Java ThreadPoolService was not properly handling
System.exit() in order to interrupt the threads.
Maybe that's why I did not see this issue on JDK 1.8. I will try with 1.7.
Notice we added default configuration which is not agresive:
<shutdown>testset</shutdown>
> 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)
