users@googlegroups.com] On Behalf Of Stephen Connolly
> Sent: Wednesday, May 09, 2012 11:55 AM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: Delay between job finished and node finished on unix
>
> Another thing you could look into is forked child processes having captured
>
users@googlegroups.com] On Behalf Of Stephen Connolly
Sent: Wednesday, May 09, 2012 11:55 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Delay between job finished and node finished on unix
Another thing you could look into is forked child processes having captured
stdout / stderr.
The process will n
Another thing you could look into is forked child processes having
captured stdout / stderr.
The process will not be seen as finished until all stdout/stderr has
been captured, so if your build leaves a non-daemon process hanging
around, that could be the RCA
On 9 May 2012 16:53, Stephen Connolly
On 9 May 2012 16:31, Wright, Clark wrote:
> Thank you.
>
> So how does remoting work with respect to end of job notification?
>
> My initial assumption was that it was simply waiting for the forked process
> to finish, grab the resultant return code, and update the master.
>
well you could look
Thank you.
So how does remoting work with respect to end of job notification?
My initial assumption was that it was simply waiting for the forked process to
finish, grab the resultant return code, and update the master.
Also, any pointers/suggestions as to what information I need/want to get ou
On 9 May 2012 15:59, Wright, Clark wrote:
> I have a set of 12 hour builds that run across 45 nodes on 3 machines (4 if
> you count the master).
>
>
>
> All the machines are Red Hat Enterprise.
>
> All the communication is via ssh (both job launch and node startup).
>
>
>
> Here is the problem I a
