Skip to content
Sign in
Success

#2952 (Feb 17, 2026, 8:55:01 AM)

Started 9 hr 33 min ago
Took 2 min 36 sec on build4-deb12build-ansible
Build Artifacts

Started by timer

This run spent:

  • 37 ms waiting;
  • 2 min 36 sec build duration;
  • 2 min 36 sec total from scheduled to completion.
Revision: 508960344b6dc51852256bf150dff1c64f2f66cb
Repository: https://gerrit.osmocom.org/osmo-ttcn3-hacks
  • origin/master
Tests (no failures)
    Makefile: clean-logs: also remove *.merged

    Change-Id: I6efe839ae2d527387b533fd110965335c0f850c9
    Vadim Yanitskiy at
    bts: as_rsl_meas_res(): tolerate low RxLev in early reports

    The MS is not guaranteed to begin transmitting immediately after
    activation of the respective logical channel.  There is typically a
    short interval during which the BTS receives no bursts.  Consequently,
    the initial RSL measurement reports are expected to indicate poor
    RxLev/RxQual values.

    We already tolerate bad RxQual values;  however, sporadic failures
    still occur due to low RxLev in the very first report.  Extend the
    logic in f_build_meas_res_tmpl() to tolerate low RxLev as well.

    Change-Id: Ic632917d429ec597dba524bf79749944cf1fc628
    Related: 8ce558dd ("bts: as_rsl_meas_res(): tolerate bad RxQual in early reports")
    Related: OS#6933
    Vadim Yanitskiy at
    hnbgw: TC_rab_assign_mgcp_to: Allow hnbgw to tear down CN conn at SCCP level

    Newer versions of osmo-hnbgw will be tearing down the CN conn at SCCP
    level by transmitting an RLSD in this scenario, instead of sending a Iu
    RANAP Release Request crafted by the osmo-hnbgw itself.
    The HNBGW is expected to forward RANAP messages between UE/HNB and CN,
    not to generate them.

    Related: SYS#7294
    Change-Id: Idb062a072c7403442ce981c6c9caeb7effb86554
    Pau Espin Pedrol at