Hmm, too bad this does not work. Seems like a bug in both of these components (surefire and failsafe). I dont know of an easy way to have the child process detect parent death that would be cross platform compatible. Perhaps a pipe can be set up between the two and the child can try to write to it every once and awhile and if that fails the child process can terminate. I dont know if either of the components can be extended to use such approach.
Jerry C 2011/2/17 Jörn Kottmann (JIRA) <[email protected]> > > [ > https://issues.apache.org/jira/browse/UIMA-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995730#comment-12995730] > > Jörn Kottmann edited comment on UIMA-2056 at 2/17/11 9:20 AM: > -------------------------------------------------------------- > > The switch to failsafe does not solve the problem on hudson. If terminated > via the abort button the process still stays alive. > > was (Author: joern): > The switch to failsafe does not solve the problem. > > > UIMA-AS extended test does not terminate reliable > > ------------------------------------------------- > > > > Key: UIMA-2056 > > URL: https://issues.apache.org/jira/browse/UIMA-2056 > > Project: UIMA > > Issue Type: Improvement > > Components: Build, Packaging and Test > > Reporter: Jörn Kottmann > > Assignee: Jörn Kottmann > > Priority: Trivial > > > > The maven process forks a process to run unit tests in. It turned out > that the forked process does not terminate if maven is stopped via ctrl+c > (maybe windows only) or terminated on hudson (via timout or abort button). > > To fix this problem it was suggested on the builds mail to switch from > surefire to failsafe. > > > http://mail-archives.apache.org/mod_mbox/www-builds/201102.mbox/%[email protected]%3E > > The extended test will be switched to the failsafe plugin. > > -- > This message is automatically generated by JIRA. > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > > >
