We need osmo_interact_vty.py in order to obtain talloc reports for
each test case automatically. See [1] for more details.
Change-Id: Ida8e08e7fe4f171f934a2d4eef4568da7c398f5c
Related: [1] I1b03b17426d8760c55976e3b78ca2f3af248c055
Wrap the original entrypoint script with a custom one that also runs a
loop in the background, which periodically lets redmine fetch git
repositories. When repositories are fetched, redmine interpretes
"closes" etc. in commit messages to mark issues as resolved.
Closes: OS#5331
Change-Id: I2a65fd6be22ae541a93c08c71cf286e4b5ad370f
Write a line like 'Misc_Helpers.mp_osmo_repo := "nightly"' into the
TTCN-3 config file (e.g. BSC_Tests.cfg), before starting the testsuite.
This allows executing different code paths in the tests based on the
repository.
Related: OS#5327
Change-Id: Ic06532f7a67e59458652c5cf4c8f6fee8113e703
Setting a non-existing parameter makes TITAN unhappy:
HC@fd91bc0a2114: Error while setting parameter field
'STP_Tests_M3UA.mp_osmo_stp_newer_than_1_4_0' to 'true':
Module parameter cannot be set, because no parameter with
name 'mp_osmo_stp_newer_than_1_4_0' exists in module
'STP_Tests_M3UA'.
Change-Id: Ie4fba3eb73e0da60bc20859efddecc5ec816cb9e
New osmo-pcu 1.0.0 which supports all expected features. Hence we can
drop special quirks to have tests passing in latest.
Change-Id: Ieb85dac479e6960e4160767e514084b80edd297b
this requires a local patch to ruby-openid, as it apparently doesn't
suppor rails 5.x (Paramters are not a hash anymore, hence lenth
method cannot be used)
Change-Id: I028d6d72757abf5d990ca2e8327e5f0a9fe3d333
The failing test case should never run. The framerelay must run
it's test with dialect NS2_DIALECT_STATIC_RESETBLOCK
Change-Id: I2b1ae7cbe26c94a4a66b6a456b76b864251e0acb
Since current master, osmo-pcu and osmo-bsc support Address Neighbor
Resolution using new PCUIF over IPA multiplex, deprecating the old CTRL
interface used until now.
Since the old CTRL interface is not yet removed in order to avoid
breakage of old deployments (only marked as
deprecated and not used by default), let's keep support to run the
existing tests with the old interface to keep them being tested in
latest release, while instruction both osmo-pcu and TTCN3 PCU_Tests to
use the new interface in master.
Once we do a new osmo-pcu release, we can drop support for the old
interface in tests, and drop it completely from osmo-pcu over the
following next release.
Depends: osmo-ttcn3-hacks.git Change-Id I05f1aabc64fc5bc4740b0d8afd8990b485eacd50
Related: SYS#4971
Change-Id: I01d0604f294dc88dc32137c976f424655849d57e
The SNS tests need both NSVCs. The NS_Tests.sns.cfg from the
ttcn3 repository can be used as reference.
Change-Id: I92f2ca61af1e3d0427e6810eddab8f2d6299242d
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
Vadim Yanitskiy
Oliver Smith
Pau Espin
Harald Welte
Alexander Couzens
Philipp Maier
Daniel Willmann