This uses the debian-nginx container "ankitrgadiya/cgit:debian-nginx"
and adds pygments for syntax highlighting, as well as the osmocom
commit filter for linking to gerrit change-ids as well as
redmine issues
Change-Id: Iec75769a972950ed9df95d5b36aa930daad1565a
The configuration of osmo-bsc currently only supports halfrate
traffic channels. In order to test assignments which contain
half rate codecs we also have to have halfrate channels available.
Change-Id: Ibcce03ab0c98545a1f316d88e1f3dd75e2ff65e1
Related: OS#3100
Related: OS#3095
Allow the osmo-bsc-main docker container to reach the virtual MGW set up by the
ttcn3-bsc-tests.
The module parameter mp_test_ip sets the IP address at which the virtual
services are set up to listen for connections -- currently actually only the
virtual MGW. Set this to 172.18.2.203 instead of using the default 127.0.0.1.
This fixes the second half of the disconnect between BSC and virtual MGW in
this docker setup. The first half is Ib53f000ec7e717b14a3e5df6e803d3d0950b937f
Change-Id: I3038481ed0bba1084b63dc6a6d2ff6e970100890
The osmo-bsc-main docker container is run in a separate docker container and
cannot reach the virtual MGW set up by the ttcn3-bsc-tests.
From ttcn3-bsc-tests/jenkins.sh it is clear that the tests are run at IP
172.18.2.203. Add this as the 'mgw remote-ip' setting in
ttcn3-bsc-tests/osmo-bsc.cfg.
This fixes the first half of the disconnect between BSC and virtual MGW in this
docker setup. The second half is I3038481ed0bba1084b63dc6a6d2ff6e970100890.
Change-Id: Ib53f000ec7e717b14a3e5df6e803d3d0950b937f
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.
Debian 9.0 ships with titan 6.1.0 which for some unknown reasons
causes segfaults in the C++ part when parsing CTRL messages and
according to TITAN project is not supported anymore anyway.
So let's use a 6.3.x build, or whatever is the highest version in
the network:osmocom:latest feed instead.
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.
the BSC configuration currently only offers A50 (no) encryption.
Since the TTCN3 tests also cover assignment tests with encryption
and osmo-bsc now supports multiple cipher settings at a time this
setting should be extended accordingly.
- Also enable A51 and A53 encryption.
Test TC_pdp6_act_deact_pcodns checks the 2 DNS values against matched
configuration. If osmo-ggsn.cfg doesn't have a 2nd DNS configured, it
won't sent the related PCO in the response, and the test will fail.
This way the address is reachable for ggsn system and can route the
packet correctly.
This commit fixes runtime failures of
GGSN_Tests.TC_pdp4_act_deact_gtpu_access when running inside the
container, since that test uses the DNS address to attempt a ping and
waits for a response. If the address is non reachable/routable from
osmo-ggsn tun, then the packet is dropped by the kernel and no ping
response is sent back.
Since October 2017 the default config name no longer has an underscore
but a dash in the filename. See osmo-sgsn.git Change-Id
If804da17a7481e79e000fe40ae0d9c4be9722e61
This uses osmo-ttcn3-hacks Change-Id
I3db452e24e5238aa05254d903739c64d202e61db, which introduces
some shared/common config file as well as per-testcase pcap file
generation.