Fix the TC_si2quater_* test fallout.
When adjusting the bsc AoIP test config, forgot to also adjust the SCCPlite
test suite config, which caused fallout in the SCCPlite tests.
Related: Idbcc703ace7012fb395f0eef3e445df28b368d74 (docker-playground)
Related: Iac46ee2cc5bc0978d5f5baa550baf493a7c56b1b (osmo-ttcn3-hacks)
Change-Id: I810ff6f89d722e7274046c360a2cbebf6f6ee53a
The bsc/BSC_Tests_CBSP.ttcn rely on a configuration where the first three BTS
carry out SMSCB messaging, and the fourth BTS does not. That requires a CBCH
channel config on bts 0, 1, 2.
Related: Iac46ee2cc5bc0978d5f5baa550baf493a7c56b1b (osmo-ttcn3-hacks)
Change-Id: Idbcc703ace7012fb395f0eef3e445df28b368d74
When my disk runs full, jenkins-common.sh fails to create a VOL_BASEDIR right
at the start, and hence no testsuite gets its external volumes mounted
properly. However, the test suite still starts up with missing cfg files etc,
and fails in non-obvious ways, until I find out the disk is full some minutes
later. Instead, verify that the base dir really exists or bail out right there.
Change-Id: I6540797c8e0ee3e7b09d4a80592d5e270e7d9adc
As it turns out, test cases from BTS_Tests_SMSCB configure the
CBCH slots "on the fly" depending on the test case parameters.
This configuration also makes some test cases fail, so let's
(re)configure SDCCH8+CBCH timeslots to SDCCH8.
Change-Id: I3699450542dc1350971fbf87ad60a330428dec27
Since osmo-bts.git 0a6bdb024f5429a35c56178496158c9b1c3ee032, the process
is quickly terminated during shutdown if no TRX is running. Since in the
OML tests the TTCN3 components implements the OML IPA server side, most
of the time when osmo-bts starts it finds no one listening on the
address and exits immediately. This makes respawn.sh script run osmo-bts
lots of times per seconds (since osmo-bts terminates quicker now). As a
result, it quickly consumes the 500 launch threshold and exits without
starting osmo-bts being launched anymore.
As a result, only first tests pass, and all the later ones fail because
osmo-bts never connects.
Let's add a sleep 1 between respawns in respawn.sh only when running OML
tests (not needed in the others since there's an osmo-bsc always
running). This also clears a lot of output in the logs of osmo-bts
processes restarting over and over again.
Change-Id: I10d3e1ef8325dd78f9ae2b95fbfd1c6d893bf8a4
gr-gsm-master is using it but it cannot be overriden. Similarly iy can
be helpful to do so in temporarliy modified images when testing
libosmocore features.
Change-Id: Ia9f26f3513da339d2255a0f6b2277682fe15bdf2
Adjust the SCCPlite osmo-bsc.cfg according to changes applied in osmo-bsc.cfg,
which were obviously forgotten to also apply to the SCCPlite test runs.
Do the same logging in both SCCPlite and AoIP osmo-bsc.cfg.
Change-Id: I4a8fe459ec580078228c6775df357b6e0acbbb03
When launching osmo-stp-master from ttcn3-bsc-test, set ulimit=-1 to allow core
files.
In osmo-stp-master set WORKDIR to /data to hopefully get the core file ending
up there without the need to set a /proc/sys/kernel/core_pattern globally in
the jenkins slave.
Change-Id: Idd67fcb3f564b9cff9b4596bf639ed1bd1b58daf
Adjust the SCCPlite osmo-bsc.cfg according to changes applied in osmo-bsc.cfg,
which were obviously forgotten to also apply to the SCCPlite test runs.
Make the SI2quater config reflect that of the AoIP osmo-bsc.cfg.
Change-Id: I4dbabcc28309424a336d2a052a067484d17663ac
Adjust the SCCPlite osmo-bsc.cfg according to changes applied in osmo-bsc.cfg,
which were obviously forgotten to also apply to the SCCPlite test runs.
These handover config changes should fix the TC_ho_* tests in
ttcn3-bsc-sccplite.
Change-Id: I9694863b2db6be6384d1d6ffb35fc477fe774d02
Forgot to also adjust the SCCPlite structure in previous commit
c7b52048e6, which broke SCCPlite testing.
Change-Id: I923e398ccd4bdd31c8325de1a850fe4c3236db79
This only enables ttcn to be able to connect multiple MSCs. To be able to use
this in the BSC_Tests, osmo-bsc.cfg needs adjusting in an upcoming patch; tests
using this are in osmo-ttcn3-hacks I21cbab193cd0de2e5692665442eae113d5f61904.
Depends: Ibb36695b7c31f7b04eec6c5d59522fc0779b3c2f (osmo-ttcn3-hacks)
Change-Id: I1986e4ef43beee161c82193694421b56136c1afe
It is needed by some user manuals using code snippet syntax
higlhlighting, such as osmo-gsm-tester one:
"""
[source,python]
----
sleep(3) # sleep for 3 seconds
----
"""
asciidoc: WARNING: test_api.adoc: line 19: filter non-zero exit code: source-highlight -f xhtml -s python: returned 127
asciidoc: WARNING: test_api.adoc: line 19: no output from filter: source-highlight -f xhtml -s python
Change-Id: I8427179f7cfc0c9150e5327803ca89adffedb8f1
The test mentioned above is added in osmo-ttcn3-hacks.git
Ieb7444c6312bbeab64da2732393b3facf3e1f003.
config files are updated to make sense:
* "nominal power" in osmo-bsc.cfg reflects correct default nominal tx
power of fake_trx.
* "osmotrx tx-attenuation" in osmo-bts.cfg is removed to let osmo-bts
use the value received through OML (max_power_red 20).
* "power-ramp step-size" in osmo-bts.cfg is increased to speed up the
test. There's no good reason to keep it lower.
Change-Id: I878d329dde3d2089ee3b68f56271fcb88d210025
This allows easily checking if fake_trx fails to start early during
startup, for instance due to a python exception.
Change-Id: I3e13a3b1f78d071618e4848aa19bcba1eb300d18
By default, Debian's package manager (apt) would install as many
dependencies as possible, including optional (recommended and
suggested) ones.
Package 'eclipse-titan' recommends 'default-jdk', which is
absolutely not needed for osmo-ttcn3-hacks, and in its turn
depends on +100500 more packages like xorg, wayland, etc.
This change significantly reduces total amount of dependencies
and the overall build time by disabling installation of
recommended and suggested dependencies.
Change-Id: I56f0d0f37e212b15e8c19ddea96d1c999177eb17
Unfortunately, we have to revert a part of change [1], because it
broke ttcn3-msc-test-latest. The reason is that the latest release
of osmo-msc does not support 'timer vlr T3212 30'.
Change-Id: Iaeb6f1ffee9286394654bc3cf9d985ace7829110
Adjust the Dockerfiles, so 'docker_images_require osmo-mgw-master-centos8'
etc. result in a centos8 based image. centos8-build already configures the
Osmocom nightly repository, so we only need to configure it for
debian-stretch.
Related: OS#4564
Change-Id: I6579748056ce0505304378b342a698b98c77fd18
Make it possible to call the ttcn3-*/jenkins.sh scripts with:
IMAGE_SUFFIX="master-centos8"
The existing docker_images_require lines of these jenkins.sh scripts
will then call docker_images_require with arguments like
"osmo-mgw-master-centos8". For example, from ttcn3-mgw-test/jenkins.sh:
docker_images_require \
"osmo-mgw-$IMAGE_SUFFIX" \
"ttcn3-mgw-test"
Let docker_images_require build the image from
osmo-mgw-master/Dockerfile (-centos8 is cut off from the dirname) and
with DISTRO=centos8 as argument.
Collisions with the debian-stretch images are avoided by setting IMAGE
to the full image name (e.g. osmo-mgw-master-centos8).
Related: OS#4564
Change-Id: I598a262fe1a7ed4dd89e13c53e4ded103c6e3b91
Prepare for distro-specific osmo-* images. While at it, put each
--build-arg on a separate line for readability.
Related: OS#4564
Change-Id: I1bf1c46295035a073e440faea3696ce53e7d7985
Don't list debian-stretch-build and debian-stretch-titan as dependencies
anymore, now that docker_images_require finds them automatically.
Related: OS#4564
Change-Id: I3cb6b693f3dd9df84fb29c0217bb3dae454cc18f
Add a function to automatically resolve the most common dependencies,
osmo-* need debian-stretch-build and ttcn3-* need debian-stretch-titan.
Do this in a shell function in jenkins-common.sh, so we can extend it in
the next patch with distribution specific dependencies (osmo-*-centos8
needs centos8-build).
Related: OS#4564
Change-Id: I98760c6dc3206529c0e267338c9f6f8e1d5be33a
Create centos8-build similar to debian-stretch-build, as preparation for
ttcn-3 tests on centos 8.
Related: OS#4564
Change-Id: Ide1e88c92b7ac301f0ea8ca110c1b2eb43f9d5ad
EGPRS Packet Channel Request cannot be enabled in 'GPRS only' mode
anyway. Moreover, this command was deprecated. Let's just remove it.
Change-Id: I03733490d9c4bf78a748d22874e550e015fbab78
In the recent osmo-bsc master, this configuration parameter has
been removed, so it fails to start due to "unknown parameter".
Change-Id: I8f763a4b35f80f4db637bebdd8e802a835a9fd2d
This is needed for the forthcoming frequency hopping test cases.
Change-Id: Ib5ad31388ae25399ad09739aac3fdcb0b3a1f78b
Depends: I86afb55ecc6703ce7a229aaa626223f9331a4778
Related: OS#4546
Prepare the repo-install-test to be extended to cover centos8 as well.
The scripts from docker-repo-install-test will be moved to osmo-ci.git
as shared code, and extended to work with centos8 too (using this new
image) in I399360ee6389591180859b52f0ef08883447b90b (osmo-ci).
Related: OS#4563
Change-Id: I50743c304728444ede8e0d40b8abef9d17c44d8d
This configuration option is unused. Related: the IMSI filtering access list is
being dropped from osmo-bsc, which might cause test fallout.
Related: I89727af5387e8360362e995fdee959883c37d89a (osmo-bsc)
Change-Id: Ied8d766ba230b93cb1185fc8b1a77f5540dfdbc1
osmo-bsc does not use an rtp-base for years, ever since we're using an MGW.
Related: Id14fa3066ca5d472a817593074a6222f159168a8
Change-Id: I267840ecb816e9de6d89ebbacb3e296c59fad57c
Neels Hofmeyr
Vadim Yanitskiy
Pau Espin
Oliver Smith