est for you, and they
> may help you help the maintainers by isolating the specific cause of the
> case which you are seeing.
>
> Mark Waite
>
>
> On Mon, May 12, 2014 at 3:53 AM, Andrei Neculau
> wrote:
>
>> Seeing the same behaviour still.
>> Does anyone ha
Seeing the same behaviour still.
Does anyone have any updates?
On Thursday, October 24, 2013 9:06:59 PM UTC+2, nigelm wrote:
>
> Actually, I have also recently upgraded to the git plugin 2.0, and am also
> seeing it repeatedly building (each time reporting many "SCM Change")
> followed by it reb
looks like this is a bug https://issues.jenkins-ci.org/browse/JENKINS-22641
On Thursday, April 17, 2014 10:49:48 AM UTC+2, Andrei Neculau wrote:
>
> *Side note*
>
> if I remove the "killall python || true" line, then I even get a warning
> at the end of the job "P
*Side note*
if I remove the "killall python || true" line, then I even get a warning at
the end of the job "Process leaked file descriptors. See
http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build
for more information"
So jenkins does see that there are spawned processes.
Hi
I have a simple job running
java -version
killall python || true
python -m SimpleHTTPServer &
but the python job is still running after the job run has ended.
Sys info: https://gist.github.com/andreineculau/10965094
On IRC #jenkins, I learned last night that the ProcessTreeKiller featur
