Jeknins leaking processes (was Re: Reset GSM tester state?)

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Harald Welte laforge at gnumonks.org
Tue Jan 29 00:33:11 UTC 2019


Hi Pau,

On Mon, Jan 28, 2019 at 09:30:36PM +0100, Pau Espin Pedrol wrote:
> that happens from time to time because while running a job in there, the
> jenkins connection between jenkins master and slave fails. As a result,
> jenkins decides it's a good idea to kill -9 osmo-gsm-tester process,
> leaving as a result its child processes alive without anybody controlling
> them.

FYI, this leaking ofprocesses is a known bug in Jenkins since 2013 (!)
which many people raised at
https://issues.jenkins-ci.org/browse/JENKINS-17116

It's a real pity that such an importan bug doesn't seem to get fixed
by Jenkins upstream.  If there are any Java developers with some spare
cycles reading here, it would really be great if you could contribue a
related fix upstream. Thanks!

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



More information about the OpenBSC mailing list