In Change-Id I6904520d8c2f546327029777d68b1907611a8cf5 of
osmo-ttcn3-hacks, we change the structure of NSConfiguration. Let's
adjust the configs accordingly.
Change-Id: I8c5e59e79b69c13632d69f5011be9279b827a4fa
Depends: osmo-ttcn3-hacks I6904520d8c2f546327029777d68b1907611a8cf5
In osmo-ttcn3-hacks Change-Id I0b4fda96accef401ffc009010f9f5621583fd6dd
we introduce the address_family member; let's make sure all configs use
it as expected.
Change-Id: I52e8b11f047a7a2ecce18e4a4f9ff3ed495a0352
Default is MNCCv7 since osmo-ttcn3-hacks.git
I5448ff931ec33f24f4837a51376f1703fe97683b, but latest tagged version of
osmo-msc only supports MNCCv6.
Change-Id: Iaac2f5453214dfcf6efd070f6ea1212a7833eb1b
Keep it using the older version in MNCC_Emulation for older versions of
osmo-sip-connector (last tagged released), since those doesn't support
MNCC7 yet.
Change-Id: I5dbacdd4bd8110b7f6cf6bdb561af420b65c035f
module param mp_enable_osmux_test is dropped in osmo-ttcn3-hacks.git
I8bc0551ec91a5fd8ea2f291a1e16a06a739c7a75.
module param mp_enable_crashing_tests is introduced in
osmo-ttcn3-hacks.git I46f1066323e19dfe708402a8c9c68e257f62751c.
Change-Id: I22bb43ba6d15eabcc731a2c3ef7aabc4f250d508
In BTS_Tests_SMSCB, we dynamically configure the CBCH slots via
the VTY interface, so there is no need to set them here. This
was also the reason of some SMSCB test case failures, because
the BSC would send unexpected LOAD INDICATIONs.
Change-Id: I6e005ca772e26878c7b19df0d854936d7b7718dd
Related: SYS#4868, OS#4708
Adjust osmo-bsc.cfg to work with osmo-bsc
Icaa2775cc20a99227dabe38a775ff808b374cf98 and osmo-ttcn3-hacks
I7eea0dd39de50ed80af79e0f10c836b8685d8644.
Related: Icaa2775cc20a99227dabe38a775ff808b374cf98 (osmo-bsc)
Related: I7eea0dd39de50ed80af79e0f10c836b8685d8644 (osmo-ttcn3-hacks)
Related: OS#4702
Change-Id: I9e9760121265b3661f1c179610e975cf7a0873f1
As of osmo-ttcn3-hacks.git Change-Id I4976d9bb1f07c8ab4ffa02848414f8ddd1bdfd3f
the test suite expects the MSC to send a CommonID to the BSC. As
older/existing tagged osmo-msc don't do that, we needt odisable that
check when verifying 'latest'.
Change-Id: If2e4cc41cb7b5758a78d694d62b34390a08e6387
Related: OS#2969
The config file of osmo-mgw has an incorrect indentation. Also no E1
trunk is configured, so that the E1 related tests fail. Lets fix this.
Change-Id: I3b19afc0809bd56e9fe0f5e968e1c000d29f4abd
We cannot rely on every test slave always having proper IPv6
conenctivity to a public DNS server, and that DNS server to respond
to ICMPv6 echo request. We're testing half of the internet instead
of our GGSN. Let's use the IPv6 address of the docker container
running the test sute, which is guaranteed to always exist. We have
no problems with routing, as the ICMPv6 is hand-crafted and encapsulated
into GTP before it's sent to the kernel IP stack - so basically on the
transmit side, the kernel doesn't know anything about the destination
address of the encapsulated IPv6 packet.
Closes: OS#4713
Change-Id: I1377ffa2cc6980168297d5ff5c81fa5dad94d7a9
When introducing IPv6 support, we map the third digit of the IPv4
address (X) to the 6th byte of an IPv6 prefix "fd02:db8:X::/64"
However, the docker daemon seems to use "fd02:db8:1::/64" internally
for its default network, so creating a docker network with the same
IP address is failing.
Let's move the MSC test suite to another sub-net (1->20) to avoid
related problems.
Change-Id: I9c5f9b96d5523eae09f3f2e6c813e9e0d047f9ab
Not only append ':hopping' to classnames equal 'BTS_Tests', but
also 'BTS_Tests_SMSCB' and 'BTS_Tests_LAPDm', so they would not
shadow non-hopping test cases in the test results analyzer.
Change-Id: Ie6ed7844c2d0dfd839181bce971506284da03d28
Related: SYS#4868, OS#4546
Apparently, TITAN concatenates the contents of all sections, so
we end up with the following set of test cases:
[EXECUTE]
BTS_Tests.control
BTS_Tests_SMSCB.control
BTS_Tests_LAPDm.control
BTS_Tests.control
Change-Id: I71802daec4a5591cbf0fce59a4247027f8dfca46
Related: SYS#4868, OS#4546
Let's use separate directories to store the artifacts of different
TTCN-3 test case groups. This would prevent the test suite from
overwriting *.log and *.pcap files when running both generic and
hopping configurations together, and simplify the overall hierarchy.
Change-Id: I7c41cfb395047433e22e9c65c8c00ae284717b32
Related: SYS#4868, OS#4546
We previously only allocated IPv4 sub-nets to the network segments
created with 'docker network'. Let's fix that by assigning both
IPv4 and IPv6 address ranges to each docker network.
Related: OS#4700
Change-Id: I8802208fddcce1ffa57e5626575d23d02b320d99
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
Harald Welte
Philipp Maier
Daniel Willmann
Vadim Yanitskiy
Pau Espin
Neels Hofmeyr