We need to update the MSC_Tests.cfg as well as the osmo-stp.cfg
to provsion a virtual RNC link. As the new RNC uses routing key 2,
we shift the MSC routing key to 3.
Change-Id: I10a249b1a851436fd3c20face6ccc94b304bd3e4
This is quite useful when looking at jenkins logs to know which exact
version was built at the time.
Change-Id: Id52c382b454e2beecf46820752aeff15b2c1a0ae
Remove hardcoded /usr/local/bin/ paths from jenkins.sh. This caused the
*-latest tests to fail, as they have the Osmocom binaries in /usr/bin
instead of /usr/local/bin.
Related: OS#3767
Change-Id: I9d1427e66028ffd15fed211b2dab5adc37718666
Default value "master" of the IMAGE_SUFFIX environment variable can be
changed to "latest" to test the latest stable builds instead of the
nightly ones. Use docker_images_require() to make sure that the required
images are existing and up-to-date before running the tests.
Related: OS#3268
Change-Id: Idbb708ab16cb71bab5069127945b63388222369e
Instead of hardcoding laforge's username in all FROM statements in the
Dockerfiles, make use of the USER variable (as passed through by the
"make/Makefile" with "docker build --build-arg USER=..."). Thanks to
fixeria for proposing this fix!
This requires running docker-ce, old versions of docker (such as the
one in the official repositories of the latest Fedora) don't support
variables in the FROM line. But docker-ce can be installed after
adding docker's 3rd party repositories.
Closes: OS#3457
Change-Id: Ic5f11c8a4e247f632cb6aea6d147e94c53e0130f
Previous to this commit, log messages were not being merged if tests
were resolved as failed (test-suite.sh ending with exit code != 0),
which can happen if at least one test failed.
Change-Id: If293fc2d3182ef2a7b997faa8b41129a9dd89c45
To remove code dup and prepare a change to where logs are written, add
collect_logs() to jenkins_common.sh and call that from each jenkins.sh after
the tests are done.
The 'rm -rf' is already done before a test starts. No need to do that again
after each test.
Change-Id: I5d8472ec36b07c828685b1bd7718e31392d168a3
After merging Change-Id: Ie844c4de62e0ef5d5c4c366185968211a7f6d676
in osmo-ttcn3-hacks, the module parameters for BSSAP configuration
require one extra argument.
Change-Id: I2a0011bc6f7bdf013005d1ea36da591673344eed
Related: OS#2544
This is no longer needed as the fix for https://osmocom.org/issues/2718
has been merged to master of osmo-ttcn3-hacks
Change-Id: Ia0c1c134405fdbce1c65059d705827f1a643e774
Related: OS#2718
the routink key for virt-bsc0-0 and virt-bsc1-0 is the same
(0), virt-bsc0-0 and virt-bsc1-0 should use different routing
keys.
- Keep the routing key of virt-bsc1-0 and assign routing key 1
to virt-bsc1-0
Change-Id: I1380ba389dc777cdac84677588b85759cad4bc14
In Change-Id: Ie7780750f7032453951f6849ecee6ab7cc34e8c2 we not only
introduced a MSC_Tests.default with syntax errors, but also a
osmo-stp.cfg with syntax errors :((
Change-Id: If7a7ff3d7ddb255654d14fe17033390214fe5341
The MSC_Tests.ttcn testsuite is now able to present multiple BSC
to the MSC (IUT). This change requires the configuration files
of osmo-stp and of the testsuite to be changed.
- update MSC_Tests.cfg to present up to two BSCs to the MSC
- update osmo-stp.cfg to support the additional connection
from the testsuite
Change-Id: Ie7780750f7032453951f6849ecee6ab7cc34e8c2
Depends: osmo-ttcn3-hacks I52a4c8118828c1605cf672889982f987568ad17d
Related: OS#1609
In the past, MM INFO transmission was broken, so the tests were
written without expecting it. Now, the bug in osmo-msc has been
fixed.
With the config file enabling it, and the tests not expecting MM INFO,
a lot of them failed. Let's disable MM INFO for now until the tests
can deal with it
We recently introduced verification of the MCC/MNC, and the osmo-msc.cfg
MCC/MNC settings mis-matched those of MSC_Tests.ttcn resulting in lots
of test failures.
In osmo-ttcn3-hacks, we have removed the *.control from the *.default
files, so let's add it here in the config files. You can now change
the tests to be executed by simply editing the config here.
This uses osmo-ttcn3-hacks Change-Id
I3db452e24e5238aa05254d903739c64d202e61db, which introduces
some shared/common config file as well as per-testcase pcap file
generation.
Ideally we would want to launch a group of containers with their own
private network segment and use the same static IP addresses in those
isolated networks.
The stupidity of docker is requiring unique IPv4 addresses even on
isolated (!) networks. This means we have to manually give each of our
test setups a different subnet, and then we can at least run one
instance that test in parallel to at most one instance of each other
test.
If this weird reestriction about unique IPv4 addresses didn't exist,
we could start any number of test runs in parallel.
Harald Welte
Philipp Maier
Oliver Smith
Max
Pau Espin