Rename the option to mp_osmo_stp_newer_than_1_4_0, because I'm going to
use the variable in an upcoming osmo-ttcn3-hacks.git patch for something
unrelated to the asp quirk so we can avoid introducing another variable.
Related: osmo-ttcn3-hacks I43b1aa2c029c88c88320d40f60df46a5eb6c4c24
Related: OS#4239
Change-Id: I6a32398242b53c827a94cf65e4a35900a7c4171a
The recently added test TC_dlcx_wildcarded depends on statsd information
from osmo-mgw but in the osmo-mgw configuration no statsd is configured.
Change-Id: Ic4f0c57f56fe400bdb9a1948917f0eeb1d7e7427
Related: SYS#5535
After moving the default VTY port for osmo-pcap-client from 4237 to
4227, it is different in nightly and latest. Configure the SUT and
testsuite to use 4227 for both nightly and latest.
Related: OS#5203
Change-Id: I6d45340429925fe5e98cc4e597a01ef51e8322ae
The the following patch I61e23e264bc85eb36d07431c7839fb445c110947
introduces the stats interface on the MGCP_Test testsuite. This means
that STATSVTY.CTRL_HOSTNAME must be set up correctly, otherwise all
testcases will fail.
Change-Id: I693cc17dbf6836e7a74b34111671b6e589744a63
Related: SYS#5535
I've seen at least one instance where -EIFDOWN was returned when the
test suite was coming up. This is a race condition, as we first
have to move the netdev into the namespace and only then can configure
it. "pipework wait" only waits for its existence, not until it is up.
We cannot revert the order, as the netdev looses its state when it
is moved to a different netns.
Change-Id: I1bfb6eb925bca4e4e1901e06eed831152cddbbe2
This module parameter is never set to false anymore, since latest
already supports the feature for a while.
The module parameter will be removed soon in osmo-ttcn3-hacks, so let's
drop using it here too.
Change-Id: Idf459365e9aa42f7efd2a418cadea63ec49bdd7a
With this we'll avoid running the test in latest. This way we'll not
fail after changing the TS for the test and hence other tests won't be
affected.
Related: SYS#5309
Change-Id: If941c110501cd5f9c1d5084cc4d054e1eafb14f4
Otherwise the loopback address is used, what causes test cases
employing the RTP Emulation component to fail:
Connection refused (unexpected)
Change-Id: Ia20ccd9e6db61d7a105523648c678db90ad345eb
Allow to optionally skip listing the installed packages. This is useful
to speed up tests when running locally.
Related: osmo-dev I3d9976d07f088e2d106d23259889a4bffe1abbcb
Change-Id: Iaafb81e9ee94850ae3b6318574ad5370d74a2838
The test that needs A5/4 enables it dynamically, and a new test requires
a defined value to reset to.
This reverts commit 8005014b55.
Related: OS#4975
Depends: osmo-ttcn3-hacks I3cf36c6ef86a0db050507f3737f4b0c10dcd52ed
Change-Id: I55135ca00ef51de5cf6eaec75cfc20c21beef665
Since recently, we also have a new IMAGE_SUFFIX '2021q1-centos8'.
We cannot rely on image_suffix_is_latest() anymore, because this
prefix does not qualify as 'latest'. If one needs to enable a
feature that is only available in master, then here is a way:
if ! image_suffix_is_master; then
# Patch the configuration files
fi
Change-Id: I65df66cd2e14934bed8114618d6ffad7831d1025
Since recently (osmo-ttcn3-hacks.git
I78880098a55d1cb456011746efa0a47832a86ca8), BTS_Tests_OML use
mp_pcu_socket to set up PCUIF, which is used in some tests (like
validating forwarding of PCUIF messages PCU<->BSC).
Related: SYS#5303
Change-Id: Iac4aac8d98e2f45021858ddaa5e20ca4c6effb31
Building debian-stretch-jenkins on ARM currently results in a few
libraries getting installed for the i386 architecture. This results in
the following build failures for master-osmo-trx and master-osmo-pcu:
checking for LIBGNUTLS... no
configure: error: Package requirements (gnutls >= 2.12.0) were not met:
No package 'gnutls' found
It is weird that we are only seeing this now, the dpkg-line has been in
debian-stretch-jenkins since the Dockerfile was added to osmo-ci four
years ago in Icb0406f96b0c18e77be51ad8317c2668fb23a45e. I'm also
wondering why it was added in the first place, and if we need it
anymore. In any case, running this on anything but x86_64 does not make
sense, so disable it there.
Change-Id: I8d890b7ebc7b99a4c79779709d1e56e0a5a6d4b9
The purpose is to run osmo-ttcn3-hacks/bsc/BSC_Tests_VAMOS.ttcn with
osmo-bts-omldummy -f VAMOS
(send BTS_FEAT_VAMOS = true).
Change-Id: I2146388bf683cfba99cef5592b8b141c3a6eabb1
Adjust docker_depends and docker_dir_from_image_name for 2021q1. Extend
README.md with examples.
Related: SYS#5370
Change-Id: Icf1e3f1928658ff3d82190c4176252cf3590a1f5
Make it possible to set a different mirror for debian-stretch-titan than
for all other containers. 2021q1 doesn't have the eclipse-titan package
and it doesn't make sense to build it there.
I've thought about adding OSMOCOM_REPO_TESTSUITE_PATH and
OSMOCOM_REPO_TESTSUITE_VERSION too, but we don't have any use for these
right now. Let's add them later if we should need them.
Related: SYS#5370.
Change-Id: I7187473c2188a864b60b03789eff62e0a527404a
Allow to change the path between OSMOCOM_REPO_MIRROR and
OSMOCOM_REPO_VERSION. While at it, tweak related comments (comment above
the variable as usually, replace "repo" wording with "feed" for the
latest/nightly variable as we usually refer to it as feed), and mention
OSMOCOM_REPO_* in README.md.
In order to be able to use a different mirror for testsuite and systems
under test, the testsuite related Dockerfiles (osmocom-bb-host-master,
debian-stretch-titan) are not using OSMOCOM_REPO_PATH. We could add a
OSMOCOM_REPO_TESTSUITE_PATH on demand, as mentioned in the next commit.
Related: SYS#5370
Change-Id: I8010a4d49d4620a5c47c2ff4f909a9aeeaad7b73
Add new container to be used by osmo-ci
Icc89e20950c2aaa67b209340d1d797b76fce32d2.
Related: SYS#5370
Change-Id: Ibb55ad18d2ccf4313f52fa3e3c10d4420c84dced
it has been deprecated in libosmocore.git 2.5 years ago:
commit 7e0686c6b4b456ec4e6e15689694b1bcf96c301f
Author: Neels Hofmeyr <neels@hofmeyr.de>
Date: Mon Sep 10 20:58:52 2018 +0200
Change-Id: Ia6946fae497319a894d4e664ac8642340620822e
Otherwise it will try to connect to 127.0.0.1.
Fixes jenkins ttcn3 test TC_sns_1c1u_unconfigured_nsvc.
Change-Id: I4b375a60c4f948c282337ca30643d14407f8239e
mongo-db is only available for x86_64 from their third party
repository. Don't attempt to install it for another architecture. As
this is part of the open5gs dependencies, don't install any of them
either.
This should fix the currently failing "update-osmo-ci-on-slaves"
jenkins job. I've considered disabling the build of the osmo-gsm-tester
container for ARM altogether, but the osmo-gsm-tester manual explicitly
mentions ARM trails.
Change-Id: Ieed36b1adf4b9ae147c7ee7ade22d4855c3dbac8
When testing gbproxy with an IP BSS, we want to use IP-SNS as that
is the more relaistic use case in practice.
This un-breaks the dockerized tests since I90bd101096979b170c38fa2a80abb80d296c4d2e
was merged in osmo-ttcn3-hacks.git
Change-Id: Id1324e019b7f148f8d33977c0089e996089e1e59
meson from open5gs requires debian10's version. physicial sysmocom OGT
setup already migrated to debian10, do the same here.
Related: SYS#4805
Change-Id: Id329726f93251b617219beeb674046065c30a436
In docker-playground.git I272e43b9be8ba53d8a815e8ab099c939f63413a7
we introduce FSM state introspection and we need to add the CTRL
hostname here.
Change-Id: Idcd77353a661cfc1685ded64b5993ff63637addc
Display an overview of installed Osmocom packages at the start of each
ttcn3-*/jenkins.sh script (and others making use of
docker_images_require).
Closes: OS#5091
Change-Id: I62670017d790fd67c6a0d8d464386c0f8e94c1a8
I used this one for building old OsmocomBB branches, which do not
compile with modern arm-none-eabi-{gcc,binutils,newlib} toolchain.
Change-Id: Ide93843836f059a3750e92a973d0a6d9cf9a5638
... which requires some modifications to osmo-ns-master
regarding pipework / docker-entrypoint.sh
Change-Id: I418f81eb1fbb2b15335ef64a3aa04d1c98a452c9
Related: SYS#5396
Oliver Smith
Philipp Maier
Harald Welte
Pau Espin
Vadim Yanitskiy
Neels Hofmeyr
Daniel Willmann