Skip to content
Sign in
Unstable

#1883 (Apr 2, 2026, 12:43:00 PM)

Started 3 hr 55 min ago
Took 9 min 47 sec on build4-deb12build-ansible
Build Artifacts

Started by timer

This run spent:

  • 4 ms waiting;
  • 9 min 47 sec build duration;
  • 9 min 47 sec total from scheduled to completion.
Revision: c4e51dbb390afefaf737d60620b9cf98fb5b0c31
Repository: https://gerrit.osmocom.org/osmo-ttcn3-hacks
  • origin/master
Tests (9 failures / ±0)Show all failed tests >>>
stp: m3ua: Expect unsolicited ASPIA ACK after unblocking ASP

Since libosmo-sigtran.git Change-Id
If32902575e874d2acc9a5fc12509af42ed151739, osmo-stp will send an
unsolicited ASPIA ACK to the peer whenever the ASP becomes unblock, in
order to somehow give a chance to the peer to notice something changed
and for instance possibly attempt re-activation of the ASP.

Related: OS#6752
Change-Id: I4b70e576beae3c386d68f17a60d6f23d1a54293a
Pau Espin Pedrol at
msc: Fix race condition in TC_reset_two(_1iu)

The test failed sporadically with:
"RAN_Emulation.ttcnpp:600 Dynamic test case error: Sending data on the
connection of port BSSAP to 659:SCCP_SP_PORT failed. (Broken pipe)"

That's because it was simply waiting for a fixed amount of time while
letting the underlaying RAN_Emulation do the RESET procedure.
Sometimes it started tearing down the test before the procedure was
fully completed, and RAN_Emulation failed passing the Reset (ACK) up the
stack because the component was already unmapped.

Fix the issue by making sure the RAN_Emulation finished the RESET
procedure before stopping the testThe test.

Change-Id: I27afd7a47e6c6cf0f70e1ecc9e26dd2c220e72ab
Pau Espin Pedrol at