Just today I've seen something relatively similar in jenkins 1.501. I was able to observe in real time how jenkins killed itself (I used strace, since jenkins had been just exiting leaving no trace of what was going on).
To cause that, a local job (scheduled in "master") was started manually, consisting of a little shell snippet which executed a python script which in turn executed "make" to build some c++ stuff. If from the console of the job I clicked on the little red cross to abort it, jenkins seemed to send SIGTERM to the process group, which must have included itself. Unless the scripts tried to defend themselves. In any case. So it goes. -- Alvaro Martinez Echevarria On Monday, February 27, 2012 8:28:04 PM UTC-8, LesMikesell wrote: > > On Mon, Feb 27, 2012 at 10:18 PM, Domen Kožar <do...@dev.si <javascript:>> > wrote: > > Just to end the story - http://travis-ci.org/ rollled out python > support, > > all my problems solved :-) > > > > It still doesn't make sense though. Does your machine just like > snakes more than coffee? > > -- > Les Mikesell > lesmi...@gmail.com <javascript:> > > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
