[
https://jira.codehaus.org/browse/MNG-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285325#comment-285325
]
Roger Pack commented on MNG-4229:
---------------------------------
I actually haven't noticed this behavior (at least not as bad...) recently, so
I had assumed it was fixed. It might not be though :P
-r
> ctrl+c interrupted maven junit tests don't actually get interrupted in windows
> ------------------------------------------------------------------------------
>
> Key: MNG-4229
> URL: https://jira.codehaus.org/browse/MNG-4229
> Project: Maven 2 & 3
> Issue Type: Bug
> Environment: windows
> Reporter: Roger Pack
> Priority: Minor
> Fix For: Issues to be reviewed for 3.x
>
>
> At least for me, the following occurs
> create a junit test that sleeps for 10s
> @Test
> public void go() throws Exception {
> System.out.println("SLEEPING 10s");
> Thread.sleep(10000);
> System.out.println("DONE SLEEPING");
> }
> interrupt it
> SLEEPING 10s
> Destroying 1 processes
> Destroying process..
> Destroyed 1 processes
> Terminate batch job (Y/N)? y
> The process continues to run despite the Destroyed message.
> Seems to be windows only [linux kills the process well]. Several different
> boxes.
> http://www.nabble.com/Destroying-process..-seems-to-fail-in-windows--td23655455.html
> No one seemed to have an answer.
> Sorry if this is the wrong place to post this.
> Thanks.
> =r
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
