Add dependencies for osmo-gsm-manuals, so we can build the release
tarballs for it (autoreconf -fi; ./configure; make dist-bzip2) in the
related jenkins job. During update of the list of projects for which we
build these tarballs, it became apparent that it was missing. Following
patches will add dependencies needed to build release tarballs for all
other projects that were missing from the list.
Related: OS#5347
Change-Id: Iba2e71b2e757bc527561d0f3e4a1af5f024a3cd7
Pull debian-stretch-titan from registry.osmocom.org if the repository is
enabled. Otherwise the image gets only pulled the first time, and does
not get updated once it becomes outdated.
Fixes: OS#5336
Change-Id: I1cf998c21e4ee1f723c3b783703e339328377f3e
Do not build debian-stretch-titan, when registry.osmocom.org is enabled.
The image that would be built at this point is not useful, since other
images like ttcn3-msc-test will use the debian-stretch-titan image from
the registry instead of the one that was just built locally.
Related: OS#5336
Change-Id: I7127e3ebac3a6a985c3ba50ba8c7cb8c5de978d9
The Iu/UMTS specific test cases in ttcn3-msc-test expect no
encryption in Security Mode Command by default (only integrity),
while osmo-msc would permit both UEA1 and UEA2 unless configured
explicitly. This causes the related test cases to fail.
A similar change was merged to osmo-ttcn3-hacks, updating the
osmo-msc.cfg in there, however the actual configuration file
that is used to execute test cases on Jenkins was not updated.
Change-Id: I43f80e3fbd73be21fb89006e16de0e1df9ba03f5
Related: https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/26389
Fixes: OS#5333
I was experiencing problems with Debian's mirrors while working on
this image, so I had to use a custom mirror list. This is a left-
over that should have been removed before merging.
Change-Id: I313bb604b09293bff8753edeefa7f78cafc9cc22
Related: SYS#5602
This enables the test suite to obtain talloc reports between the
test case executions, which get stored together with the PCAP files.
Let's see how it works with the mentioned projects first; others
can be configured later. See [1] for more details.
Change-Id: Icd4c2d80db934535d499598282ed9416d8088163
Related: [1] I1b03b17426d8760c55976e3b78ca2f3af248c055
Related: OS#5328
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
Oliver Smith
Vadim Yanitskiy
Pau Espin
Harald Welte
Alexander Couzens
Philipp Maier