Support running multiple TTCN-3 testsuites in parallel when the
jenkins.sh scripts get called from outside of jenkins too.
Closes: OS#5358
Change-Id: Iaaf5719f758553687f2ab57975be275e7ac07e36
Before this patch the printing of the junit.xml to stdout fails:
+ collect_logs
+ cat '/tmp/tmp.CzafJpQyw8/*/junit-*.log'
cat: '/tmp/tmp.CzafJpQyw8/*/junit-*.log': No such file or directory
+ true
Change-Id: I600d3bdb3de23ef6f381cd5b81e2b851856b2b9b
I don't really see the point of crating 19 MBytes of logs for every
ttcn3-bsc-* test run that consists mainly of debug messages about
sending a message from left to right. osmo-stp is not the IUT here,
but merely a part of the test fixture. Let's reduce log verbosity.
Change-Id: If1d22814d89c4e52b3b7804110256d896b7cc99f
It seems a manual 'make' in the respective directories no longer
works, as always the default distro is used as upstream reference.
Let's work around this by adding DISTRO variable assignments to the
respective makefiles.
Change-Id: I8769d504ca7afde07d4a0ad1f03aaaec892bf576
This enables the test suite to obtain talloc reports between the
test case executions, which get stored together with the PCAP files.
Change-Id: I61fef7763e6445c231ff2664036e243a9ac96ff6
Related: Icd4c2d80db934535d499598282ed9416d8088163
It's better if we run ttcn3-bts-test with the default values, given
that they were significantly reduced some time ago.
Change-Id: If8438adfdbc506d2b6b7858ea8a0ea859ba246a1
Related: I7da3d0948f38e12342fb714b29f8edc5e9d0933d (osmo-bts)
Related: OS#4487
Adjust to the package not being split in rpm packaging. This was not
noticed before, because we did not run TTCN-3 tests for osmo-pcap with
CentOS8.
Related: SYS#5754
Change-Id: I775776ff7f358fee3d085f814c295c49225f5170
Don't attempt to install libosmo-netif in this Dockerfile. I've noticed
this because we want to build osmo-pcap for CentOS7 with this container
to run the TTCN-3 tests, and we don't have libosmo-netif for CentOS7.
Add pkgconfig(libosmogb), which is required to build osmo-pcap
according to configure.ac. In Debian, this gets installed as part of
libosmocore-dev.
Related: SYS#5754
Change-Id: I9c3a3b43ee7c25c06042f3303b9edb4005e7db31
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