> On 28. Jan 2019, at 20:30, Pau Espin Pedrol <[email protected]> wrote:
>
> Hi,
Hi!
I don't know how the state works but have you considered:
* Adding stale detection, either in code or jenkins?
* far fetched.. look if subreaper can be of any help?
cheers
holger
>
> 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.
>
> I usually take care myself of removing those processes (ps -ef | grep osmo,
> kill) and cleaning state (rm /var/tmp/osmo-gsm-tester/state/*) when I see
> lots of tests failing with UNKNOWN during the more-or-less daily jenkins job.
> Unfortunately, due to being on sick leave these days it may take longer than
> usual to have this work done after a conn failure, my apologies.
>
> Thanks Neels for taking care of the issue.
>
> Kind regards,
> Pau
>
> --
> - Pau Espin Pedrol <[email protected]> http://www.sysmocom.de/
> =======================================================================
> * sysmocom - systems for mobile communications GmbH
> * Alt-Moabit 93
> * 10559 Berlin, Germany
> * Sitz / Registered office: Berlin, HRB 134158 B
> * Geschaeftsfuehrer / Managing Director: Harald Welte
