Skip to content
Success

#2667 (Jan 23, 2026, 12:23:00 PM)

Started 23 days ago
Took 14 min on build5-deb12build-ansible
Build Artifacts

Started by timer

This run spent:

  • 0.12 sec waiting;
  • 14 min build duration;
  • 14 min total from scheduled to completion.
Revision: 7c513d15cd40ce95308859127a1f43f3b8682b30
Repository: https://gerrit.osmocom.org/osmo-ttcn3-hacks
  • origin/master
Tests (no failures)
    bts: TC_rsl_chan_initial_ta: misc improvements

    Change-Id: Ifc2c850104b3710679485042ab5b7a758d0ae000
    Related: OS#6919
    Vadim Yanitskiy at
    bts: TC_rsl_chan_initial_ta: fix sporadic failures

    It may happen that an UL SACCH block is received by the BTS before a DL
    SACCH block is generated and delivered to the testcase.  In this case,
    the Timing Advance control loop may update the initial TA value that
    was set during RSL CHANnel ACTIVation.

    By default, trxcon transmits UL SACCH blocks with TA=0, which is exactly
    what triggers the TA control loop in this situation.

    To avoid this, we explicitly signal the expected TA value to trxcon by
    pre-populating the UL SACCH cache.  This is done by sending a DATA.req
    containing a measurement report in advance, before establishing DCCH,
    so that subsequent UL SACCH blocks carry the correct TA and do not
    activate the control loop.

    Additionally, take the opportunity to add missing f_L1CTL_PARAM().
    This compensates for the artificial delay introduced by
    f_trxc_fake_toffs256(), further reducing the risk of triggering
    the TA control loop.

    Change-Id: Iebb043ccc710750dff937e2281c23d343b85bda1
    Related: OS#6919
    Vadim Yanitskiy at