Skip to content
Unstable

Changes

Summary

  1. sccp: testenv: fix run with asan + latest binaries (details)
  2. testenv: remove TESTENV_GIT_DIR (details)
  3. msc: add/expect network-originated MT-Forward-SM.Err (details)
Commit 563100e13fb12b2bb0b073adeab9327778d0bb70 by Oliver Smith
sccp: testenv: fix run with asan + latest binaries

When running against osmocom:nightly:asan, build sccp_demo_user with
--enable-sanitize. Otherwise this code is not running with asan and
doesn't even start (as the libraries we link against are built with
--enable-sanitize).

When running against osmocom:latest, check out the latest tag instead of
current master.

Fixes: OS#5899
Change-Id: I5307125560694feae9f0978ebd27607a77ed8675
The file was modified_testenv/testenv/podman_install.py
Commit f10f525ce38726785bb935e124ad4591b9097c13 by Oliver Smith
testenv: remove TESTENV_GIT_DIR

This variable is not used anymore, remove it.

Change-Id: Iabb9fa3b9b393b2cb7f18fb877746e5d1e510e63
The file was modified_testenv/testenv/cmd.py
Commit a61fcf1c87c56b48e08e09b3411e2f56f6b6a8c0 by Vadim Yanitskiy
msc: add/expect network-originated MT-Forward-SM.Err

The idea is to have two variants of the MT-Forward-SM.Err:

* _MS: originated by the MS/UE (via RP-ERROR),
* _NET: originated by the network (MSC) itself.

In both testcase scenarios we expect the network to indicate the
MT_FORWARD_SM_ERROR on its own, due to the lack of response from MS/UE.
Use the right template kind for that, expect a specific Cause value.

Change-Id: Ic27d943645fdff8d34f958e3bf16c8ee6e8368d2
Related: osmo-msc.git I51d92752471147e6d21a5059bebb0702b32642a5
Related: e9de1515 ("msc: add TC_gsup_mt_sms_{paging,conn}_timeout")
Related: SYS#7323
The file was modifiedmsc/MSC_Tests.ttcn
The file was modifiedlibrary/GSUP_Templates.ttcn