ttcn3-osmo-msc was playing ping-pong for 1 d, 5h (MSC_Test-GSUP-IPA)

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/jenkins-notifications@lists.osmocom.org/.

Oliver Smith osmith at sysmocom.de
Fri May 24 13:00:46 UTC 2019


This just happened again three times in a row. I've stopped the jobs,
analyzed a bit what is going wrong, and created an issue:

https://osmocom.org/issues/4022

If somebody who is more familiar with TTCN3 could take a look at this,
it would be great.

Oliver

On 4/10/19 3:17 PM, Oliver Smith wrote:
> Same with
> 
> https://jenkins.osmocom.org/jenkins/job/ttcn3-msc-test/493/console
> 
> I've also stopped that job, and killed the remaining containers.
> 
> Regards,
> Oliver
> 
> On 3/29/19 11:19 AM, Oliver Smith wrote:
>> The job kept printing this:
>>
>>> MSC_Test-GSUP-IPA(451)@d52f00df4ec6: CCM Rx:{ msg_type := IPAC_MSGT_PING (0), u := omit }
>>> MSC_Test-GSUP-IPA(451)@d52f00df4ec6: CCM Tx:{ msg_type := IPAC_MSGT_PONG (1), u := omit }
>>
>>
>> https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-msc-test/481/console
>>
>> I have stopped it and killed the remaining docker containers with
>> ttcn3-admin.
>>
>> https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-admin/
>>
>> The job started again, and now it seems to run properly.
>>
>> Oliver
>>
> 

-- 
- Oliver Smith <osmith at sysmocom.de>            https://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



More information about the jenkins-notifications mailing list