You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Daniel Takamori (JIRA)" <ji...@apache.org> on 2016/02/19 19:05:18 UTC
[jira] [Comment Edited] (INFRA-11278) Jenkins child process still
running
[ https://issues.apache.org/jira/browse/INFRA-11278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154562#comment-15154562 ]
Daniel Takamori edited comment on INFRA-11278 at 2/19/16 6:04 PM:
------------------------------------------------------------------
[~sobkowiak] I killed the hanging process and kicked off a new build. https://builds.apache.org/view/S-Z/view/ServiceMix/job/ServiceMix-master/29/console
was (Author: pono):
[~sobkowiak] I killed the hanging process and kicked off a new build.
> Jenkins child process still running
> -----------------------------------
>
> Key: INFRA-11278
> URL: https://issues.apache.org/jira/browse/INFRA-11278
> Project: Infrastructure
> Issue Type: Bug
> Components: Jenkins
> Reporter: Krzysztof Sobkowiak
>
> I had to kill a job in https://builds.apache.org/job/ServiceMix-master but I think, the surefire process is still running. In the next build runs I can find following entry in the surefire output files
> java.net.BindException: Address already in use
> It means, there is still a process which uses the ports used by the tests. Probably killing the job did not kill the surefire process.
> Could you please cleanup the job processes?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)