Hi Mark, suffixing 0 to Exit has worked amazingly my issue has resolved.
You deserve round of applaud. Many thanks Suhas India
On Friday, April 17, 2015 at 1:51:03 AM UTC+5:30, Mark Waite wrote:
>
> I'm surprised if a process leaking a file descriptor would cause a build
> step to fail. I've
Hi Mark,
Just referred your comments and I have 0 to Exit as you shows below, and to
my surprise jenkins error has disappeared, thanks a lot
On Friday, April 17, 2015 at 1:51:03 AM UTC+5:30, Mark Waite wrote:
>
> I'm surprised if a process leaking a file descriptor would cause a build
> step
In general, you don't need to fix the message that the process leaked file
descriptors. If the process leaks file descriptors, eventually it will
exhaust the file descriptors, but that is not likely the cause of a problem
for this specific job.
If you want processes to survive beyond the end
mark,
I did run Jenkins job in executing windows batch command. But Jenkins job
itself kill all the child process.due to Runtime Environment will be down.
can you please help us, how I can fix process leaked file descriptors issue.
execute shell the command:
N:
cd CCOP\REFRESH_SCRIPTS
Super!!
It worked by adding Exit 0 in the end of batch. The process leaking file
descriptor still there, but Jenkins returns Success.
Thank you so much, Mark!
Best regards
Victoria
On Thursday, April 16, 2015 at 5:08:28 PM UTC-5, Mark Waite wrote:
I think those two lines are independent
I'm surprised if a process leaking a file descriptor would cause a build
step to fail. I've never seen it fail in any of the cases where it was
reported on my jobs.
You may want to confirm that the build step did not fail, independent of
whether or not there was a leaked file descriptor. If
I think those two lines are independent of one another. The line:
Build step 'Execute Windows batch command' marked build as failure
hints that the batch script returned a failure code to its calling
environment. I believe the default exit value for a batch script is the
exit value of the
Mark,
the particular step is to call two processes by window batch command,
those processes are successfully running after I set BUILD_ID=dontKillMe.
Jenkins job was still marked as failure:
Process leaked file descriptors. See
if it is hard to get rid of Process leaked file descriptors, is there
anyway I can make Jenkins ignore this failure step (or don't fail it), so
I can move on next step.
I am looking at Conditional buildstep plugin, but not able to figure out
how this plugin work and whether it is the right
I need to invoke two window processes in order to start our test after
Jenkins build is down. They were normally killed after being brought up,
and I receive Process leaked file descriptors. I found someone suggest to
do set BUILD_ID=dontKillMe before calling my command to start processes.
10 matches
Mail list logo
