Skip to content
Sign in
Success

#28906 (Jul 1, 2026, 11:47:42 AM)

Started 4 hr 58 min ago
Took 3.4 sec on build5-deb12build-ansible

Started by upstream project gerrit-osmo-ttcn3-hacks build number 4181
originally caused by:

This run spent:

  • 7.1 sec waiting;
  • 3.4 sec build duration;
  • 10 sec total from scheduled to completion.
Revision: a287e1c6d7687a51b1e2a4fb755124dcbbddb324
Repository: $GERRIT_REPO_URL
  • master
bts: TC_pcu_interf_ind: check reporting interval instead of absolute FN

Recent osmo-bts commit 53f0ec29 broke TC_pcu_interf_ind:

  Verdict: fail reason: Odd TDMA frame number := 935

There's no requirement that periodic interference reports must land
on a TDMA frame number satisfying 'fn mod 104 == 0' - only that they
keep arriving every configured averaging period.  Instead, verify
that the interval between consecutive reports equals 104 TDMA frames
(1 SACCH period), using the new f_gsm_fn_sub() helper.

Change-Id: Ia96f2926400bae8c0a6fb8f81eb56b48ca5f2de9
Related: 53f0ec29 ("l1sap: fix duplicate RF RESOURCE INDICATION on clock bootstrap")
Vadim Yanitskiy at