This uses the config files from osmo-ttcn3-hacks.git instead of keeping
local copies around here, which has shown many times will get out of
sync. Extract the original files (*.src.cfg) from the testsuite image
(ttcn3-bts-test) and merge them with the local *.confmerge files using
osmo-config-merge. Use the resulting files (*.gen.cfg).
Unfortunately, osmo-config-merge is not capable of removing text blocks
or substituting specific parts, so we fall-back to using sed where it's
needed. A good example is 'log gsmtap 127.0.0.1', as there is no
command for removing a logging target of such type.
Co-Authored-By: Vadim Yanitskiy <vyanitskiy@sysmocom.de>
Co-Authored-By: Oliver Smith <osmith@sysmocom.de>
Change-Id: If15461240f3037c142c176fc7da745a1701ae3f8
Since recently (osmo-ttcn3-hacks.git
I78880098a55d1cb456011746efa0a47832a86ca8), BTS_Tests_OML use
mp_pcu_socket to set up PCUIF, which is used in some tests (like
validating forwarding of PCUIF messages PCU<->BSC).
Related: SYS#5303
Change-Id: Iac4aac8d98e2f45021858ddaa5e20ca4c6effb31
It was noticed that most of the OML related TTCN-3 test cases do not
pass anymore, while some of them are green for the release builds.
The culprit is I49706926b1e962b18791174627bc3cc0cd0cd9d5, which did
not ensure backwards compatibility with older configuration files.
Let's remove 'ms-power-control dsp' and use the defaults.
Change-Id: I940df510d803d0eaa063dd5145c2f9a4c5d0543f
Configure each osmo-* program to send GSMTAP log output to the IP of the
docker container, which runs the testsuite (and therefore runs tcpdump).
Related: https://lists.osmocom.org/pipermail/openbsc/2019-June/012946.html
Change-Id: I99e74f6ffb5b7d566cec35995bf067df414968d8
Run the testsuite one more time; this time for OML tests which
require us to run without a BSC. We can run those with trxcon
and omso-bts-trx and don't need virtphy for them.
Related: OS#4031
Depends: osmo-ttcn3-hacks I82bb85b684d2db3a6b1e96a68ffde03e22affa6b
Change-Id: I97db9c74c56ca93c75e5e5226955799cd945eec0