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 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 you're building on 
> Unix, be sure that the build step reports success (exit 0 from a shell 
> script, etc.).
>
> Mark Waite
>
> On Thu, Apr 16, 2015 at 1:49 PM Victoria Wei Lei <[email protected] 
> <javascript:>> wrote:
>
>> 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 plugin to achieve above 
>> goal? 
>>
>> Please help.
>> Thanks
>> Victoria 
>>
>> On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote:
>>>
>>> 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.
>>> Good news is that the processes are able to stay. Bad news is "Process 
>>> leaked file descriptors" still occur and mark Jenkins job failed, hence, I 
>>> can't execute any test steps afterwards
>>>
>>> Any input will be highly appreciated.
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/69c8b4e3-e36a-4f45-a1b3-5f85569e03f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to