#3060 (Feb 24, 2026, 12:27:05 PM)

redmine: upgrade from 5.1.7 to 5.1.10 (security update)

Change-Id: I526679bd35baea3ba71c66b34fee9ccea44ca312

titan: upgrade to libfftranscode 0.6 (updated NGAP ASN.1 to V17.5.0)

Change-Id: I56034ef75cd6cca88fc9d353e097086bce6d639c

redmine: set session_store to active_record_store

Change the session store to fix the
"ActionDispatch::Cookies::CookieOverflow" errors we are getting.

IMPORTANT: after deploying this change, the following commands must be
executed once manually to create the session table:

  # docker compose exec redmine bash
  $ rails generate active_record:session_migration
  $ rake db:migrate

Related: OS#5476
Change-Id: Iacec800b9179cfac894f41e9eb1a5cca7e56ff1c

debian-bookworm-build: add gdb

Add gdb to display backtraces for coredumps in jenkins.

Change-Id: I0069b157501ac37ef0a6be814b3f78e7504436a8

debian-trixie-build: new container

Create a copy of debian-bookworm-build for trixie.

Change-Id: I880b5d9c57642af98c116fcb4137a54c58f5f7b4

debian-trixie-build-arm: new container

Change-Id: I1c0efb85324b70b6370ea94f74f440e639442da5

debian-trixie-build: add libgcrypt20-dev

Add libgcrypt20-dev as it is needed by open5gs's dependency
freeDiameter:

../../../../../build/src/open5gs/subprojects/freeDiameter/include/freeDiameter/meson.build:146:15: ERROR: C shared or static library 'gcrypt' not found

Without this installed, gerrit-verifications for osmo-dev fails.

Change-Id: Ifc0cc2e3900530cb75651125c0f769f8689748b2

common/Release.key: update

Source: https://obs.osmocom.org/projects/osmocom/public_key
Change-Id: I5bee715ad50830ab12472fc3946b30ec3d9ace16

gerrit: update to 3.10.9 (latest 3.10 patch release)

Change-Id: Id3f70d0a2de8b2bd640c36796e643b953f6716cb

gerrit: update to 3.11.x as 3.10.x will become EOL on November 10, 2025

see https://www.gerritcodereview.com/2025-09-17-gerrit-3.13-release-plan.html

Change-Id: Icfbed5017e867f4195ee2922331c0e76b64139a0

nplab-m3ua-test: Parametrize git branch and change it to osmocom/master

I just pushed a new "osmocom/master" branch to our fork pointing to
laforge/python3.

Change-Id: I78b2a27b355f11ba64476216bc7ef76713e8f61e

nplab-m3ua-test: Configure Network Indicator as International

That's what we are using at the osmo-stp configuration.
Until now it didn't matter since libosmo-sigtran didn't validate NI
matching configuration on received messages, but since
1af56bf8cf266dd708b623e75d6d175a58f3dd47 it does.

Change-Id: Iae825ebc588524c7a3761c80392940733f3887a6

ttcn3-bts-test: Run fake_trx with sched-prio-rr

Change-Id: Ie8c395bb7de1823ac5de951e6a66085148e9c224
Depends: osmocom-bb.git I3c7f36c17fc7b9cae1023b4a0ed37f983dc286dc

ttcn3-bts-test/jenkins.sh: tweak local vars

Make it consistent.

Change-Id: I8c5597f20428f8f274ea15f62e561562e5768460

ttcn3-bts-test: run bpftrace scripts

Add logic to run bpftrace scripts attached to osmo-bts-* while the
testsuite runs. The initial script is from Vadim:
https://gitea.osmocom.org/osmocom/bpftrace-scripts/src/branch/master/udp_sendmsg_delay.bt

Change-Id: I5c22cdbb08fe797be936ca174f65ade626fa4895

common/respawn: improve logging

Add "[$(date)] respawn:" infront of all log messages, so it is clear
that they come from this script and so we have timestamps that we can
compare. This will be useful when running the bpftrace scripts along
with osmo-bts-*, which will get restarted at the same time as the
osmo-bts-* processes.

Change-Id: I641f17f6988eced12c9b301042fb5c5cfd757511

ttcn3-bts-test: give bpftrace time to print stats

When running with bpftrace, send a kill signal to the bpftrace scripts
before killing the container. Otherwise the scripts don't print their
statistics, the end of the log then looks like this:

  [Thu Dec 18 18:06:06 UTC 2025] respawn: 2: starting: /data/bpftrace/udp_sendmsg_delay.sh
  + pidof osmo-bts-trx
  + bpftrace /data/bpftrace/udp_sendmsg_delay.bt -p 56
  Attaching 3 probes...
  Tracing udp_sendmsg() latency... Hit Ctrl-C to end.

Change-Id: I1781bddddf429c4c6a951b519a639b8663d397e6

ttcn3-bts-test: mount tracingfs only when needed

Change-Id: I59bbbc96c0686a2c8792626297e656df72e578ed

Upgrade redmine to 5.1.11 (security fixes)

As the official docker image still has 5.1.10 we're temporarily using a
custom build of the redmine base container.

Change-Id: Id06331c1f169cd02340730d5499bcb8a1ad3ea22
Closes: OS#6915

bpftrace: Introduce ksys_write_delay.bt

This will record latency of write() calls during ttcn3-bts-test run,
where some write() call on stderr seems to be taking ~0.32 seconds,
stalling the timerfd (71 times) and making osmo-bts exit.

Related: OS#6794
Change-Id: Ia1d2036ac7c6c9e2818d07e8787d857b3b3e5881

jenkins-common: use debian 13 by default

The testsuites were still using debian 12, switch to the current stable
version (13).

This also gives us a much newer bpftrace version:
* Debian 12: 0.17.0-1
* Debian 13: 0.23.2-1

Change-Id: I231e1e93724faf6d659132be9b9d0e164502bf95

debian-trixie-obs-latest: new container

Switching to debian 13 by default requires this new container for all
the -latest jobs that are still docker-playground based.

Fixes: 82bee6c4 ("jenkins-common: use debian 13 by default")
Change-Id: Id78e445ff93dbe63751f4579a52f122d524e0003

ttcn3-bts-test: add --no-warnings to bpftrace

Since switching to debian 13 and having bpftrace 0.23.2 instead of
0.17.0, bpftrace is constantly printing warnings. Turn off warnings by
default so we don't end up filling up the disk space of jenkins runners
while ttcn3-bts-test runs for >2h.

We can turn on warnings in copies of the main jenkins job for
development, while also ensuring that we only run a few tests instead of
the whole testsuite.

Warnings look like this:

  root@deb12build-ansible:/home/osmocom-build/jenkins/workspace/ttcn3-bts-test/logs/bts/bpftrace# head udp_sendmsg_delay.log
  [Thu Jan 15 01:31:13 UTC 2026] respawn: 0: starting: /data/bpftrace/udp_sendmsg_delay.sh
  + pidof osmo-bts-trx
  + bpftrace /data/bpftrace/udp_sendmsg_delay.bt -p 9
  Attaching 3 probes...
  Tracing udp_sendmsg() latency... Hit Ctrl-C to end.
  /data/bpftrace/udp_sendmsg_delay.bt:29:3-13: WARNING: Invalid argument
  Additional Info - helper: get_ns_current_pid_tgid, retcode: -22
    @start[tid] = nsecs;
    ~~~~~~~~~~
  /data/bpftrace/udp_sendmsg_delay.bt:30:3-13: WARNING: Invalid argument

Change-Id: I0e4c62f27f67d4b8601516ce5c1ebfa415331b4a

debian-trixie-obs-asan: new container

Switching to debian 13 by default requires this new container for
ttcn3-bts-test-asan.

Fixes: 82bee6c4 ("jenkins-common: use debian 13 by default")
Change-Id: Icda707751fca8a314e92200bce0e473e43e426f3

debian-trixie-build: install the osmocom:misc repo

Install the osmocom:misc repository, so we can use the latest bpftrace
version in ttcn3-bts-test.

Related: OS#6927
Change-Id: I58e91932b089a92f4f4c31814cd1fd7d202b04c0

debian-trixie-obs-latest: fix signed-by= path

Fix for:
  Error: Failed to parse keyring "/usr/share/keyrings/osmocom-misc.asc"

Fixes: 59d469 ("debian-trixie-build: install the osmocom:misc repo")
Change-Id: Ib90abcdf96fc2b555f477899bac730c6f4a76fad

ttcn3-bts-test: fail on unexpected respawn count

Suggested-by: Pau Espin Pedrol <pespin@sysmocom.de>
Change-Id: Idd9f8dcf1a7186a0715c1026da44f404c1c574d9

osmo-ns-master: drop python3-osmopy-utils / --enable-external-tests

--enable-external-tests requires python3-osmopy-utils, however this
package is no longer available for debian:10.  We're not running
tests, so it's not really needed.  Removing it fixes ttcn3-ns-test-fr.

Change-Id: I342099be87175dfe189a8906b53ee26328c0a417

common/wrapper_core_bt_on_error: import

Import this script from osmo-ci dfa9fcca
("scripts/wrapper_core_bt_on_error: new script"), so it can be used in
ttcn3-asterisk-ims-ue-test in a follow-up patch.

Change-Id: I773ff8b8c07c96e1b5b417fa28518ac7dc2e14ec

ttcn3-asterisk-ims-ue-test: show trace on coredump

Use wrapper_core_bt_on_error.sh to show a backtrace in case asterisk
crashes and a coredump is generated. Set CWD to /data, so the core and
core.backtrace files end up in the jenkins artifacts.

The result looks like this (forced a segfault in main() to test this):
  $ cat asterisk-ipv4/core.backtrace
  [New LWP 18]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/asterisk -C /etc/asterisk/asterisk.conf -f -g -vvvvv -ddddd'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x000073908c476ffb in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  #0  0x000073908c476ffb in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  #1  0x00005ba2677294dc in memset (__dest=0x0, __ch=1, __len=1) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:59
  #2  main (argc=<optimized out>, argv=0x7fff865fdd28) at asterisk.c:3839

Change-Id: Iee22cbeaa2b2c136c789afc3ebd3ec1be10a6ac7

asterisk-master: use git clone --depth=1

Speed up cloning the big asterisk git repositories.

Change-Id: Ifc0c2375482e39ecf2f34b93cf6f02a83da29990

ttcn3-bts-test: write bts logs to tmpfs

Pau suggested in the related issue that we try to write the bts logs
into tmpfs, instead of directly to ext4. This seems to cause the slow
downs, which then result in clock skew errors.

Related: SYS#6794#note-29
Change-Id: Id9a93f7149ef7e9bfde1f4fe3a8299ba46645d50