You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Roger Pack (JIRA)" <ji...@codehaus.org> on 2009/07/06 23:27:22 UTC
[jira] Created: (MNG-4229) ctrl+c interrupted maven junit tests
don't actually get interrupted in windows
ctrl+c interrupted maven junit tests don't actually get interrupted in windows
------------------------------------------------------------------------------
Key: MNG-4229
URL: http://jira.codehaus.org/browse/MNG-4229
Project: Maven 2
Issue Type: Bug
Environment: windows
Reporter: Roger Pack
Priority: Minor
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.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4229) ctrl+c interrupted maven junit tests
don't actually get interrupted in windows
Posted by "Roger Pack (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-4229) ctrl+c interrupted maven junit tests
don't actually get interrupted in windows
Posted by "Stefan Hansel (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285318#comment-285318 ]
Stefan Hansel commented on MNG-4229:
------------------------------------
mhmm - noone cared for it yet since 2009/2010 ?
We migrated to Maven this year and now get into trouble with our build-server/build-agents due to this bug.
In TeamCity there is the possibility to cancel builds - essentially this sends a CTRL-C to the running Maven process and hopes this it will properly kill the build. - Which does not happen as Surefire keeps running and our agents degrade heavily over time bause of all these unkilled processes.
Killing an Ant-Build worked a treat in the past, I'm really curious why noone else is running into this problem on a regular basis? Anyway - the proposed fix in PLXUTILS-40 does help to solve this Maven problem - I really hope it gets integrated soon.
> 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