[ https://jira.codehaus.org/browse/SUREFIRE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317069#comment-317069 ]
Andreas Gudian commented on SUREFIRE-946: ----------------------------------------- Having thought about this over night, I'm pretty sure my Surefire946KillMainProcessInReusableForkIT does not yet test anything, as a) verifier does not fork by default in the current configuration, and b) I'd have to add some code to check if the process already terminated (e.g. by checking if the thread named {{Thread.currentThread().getName()+ "-ProcessKiller"}} is still alive). I'll fix that tonight. > Maven hangs on SIGTERM when using Surefire forking > (CommandLineUtils.ProcessHook) > --------------------------------------------------------------------------------- > > Key: SUREFIRE-946 > URL: https://jira.codehaus.org/browse/SUREFIRE-946 > Project: Maven Surefire > Issue Type: Bug > Affects Versions: 2.13 > Reporter: Jesse Glick > Fix For: 2.14 > > Attachments: stack.txt, SUREFIRE-946.patch > > > Java 7u7, Surefire with JUnit {{forkMode="perthread"}} + {{threadCount="1"}} > + {{reuseForks="true"}}. After pressing Ctrl-C to stop the Maven test run, > the process hangs and must be killed with SIGKILL. From the thread dump, > {{CommandLineUtils.ProcessHook}} and {{StreamFeeder}} look responsible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira