UnstableChanges

Summary

  1. osmo-bsc.cfg: remove obsolete logging categories (cc, mgcp) (details)
  2. osmo-stp-test: Ensure we build the laforge/stp branch (details)
  3. stp: don't only execute STP_Tests.control, but also M3UA and IPA (details)
  4. repo-install-test: disable osmo-ggsn service (details)
  5. osmo-bsc-latest: remove obsolete logging categories (details)
Commit 80030e98151b73f39dc017da5366ae55f4cee42e by pmaier@sysmocom.de
osmo-bsc.cfg: remove obsolete logging categories (cc, mgcp)
The logging categories cc and mgcp are obsolete. The tests still contain
logging statements with those categories, which makes osmo-bsc terminate
during startup while parsing the configuration file.
Change-Id: Ifd6bf46b73420c0443f997ea953318710544b751
The file was modifiedttcn3-bsc-test/sccplite/osmo-bsc.cfg
The file was modifiedttcn3-bts-test/osmo-bsc.cfg
The file was modifiedttcn3-bsc-test/osmo-bsc.cfg
Commit 1e45b4d9663e458eea2a413f6d7ad354f8cacd39 by laforge
osmo-stp-test: Ensure we build the laforge/stp branch
Change-Id: I2cf300eb37b327450da0f8b20ee209a6109bf8fe Related: OS#4220
The file was modifiedttcn3-stp-test/Makefile
Commit 436fe0c1438a8915c3fc21ab5bd092bfb369d094 by laforge
stp: don't only execute STP_Tests.control, but also M3UA and IPA
Change-Id: Icc7d168dc90d3551d27c1be27c50d66dd84f0a50 Related: OS4220
The file was modifiedttcn3-stp-test/STP_Tests.cfg
Commit b6ab37d9649e5659ea04d9abbd941b1b9074c2a7 by Oliver Smith
repo-install-test: disable osmo-ggsn service
OsmoGGSN is not able to use the tun4 device from the default config in
docker. Since the more strict config checking in [1], it does not just
report a warning, but fails to start:
<0002> ggsn.c:189 APN(internet): Opening TUN device tun4
<0001> tun.c:184 errno=2/No such file or directory open() failed
<0002> ggsn.c:191 APN(internet): Failed to configure tun device
Error occurred during reading the below line:
  no shutdown
Failed to open config file: '/etc/osmocom/osmo-ggsn.cfg'
Fix the repo install test jenkins job by not checking osmo-ggsn anymore.
In theory, we could probably create the tun device on the host, and
mount it inside the docker container. But that would require some
additional logic to clean it up properly, and it does not seem worth the
effort right now.
[1] libosmocore Ic9c1b566ec4a459f03e6319cf369691903cf9d00 Change-Id:
I15c7a2f38a21cd96c9852ad26f4b4a81798e6593
The file was modifieddebian-repo-install-test/testdata/repo-install-test.sh
Commit 7cb84b0d162601da2f5d640f9fcd996e466eda3b by laforge
osmo-bsc-latest: remove obsolete logging categories
The logging categories cc and mgcp are obsolete for osmo-bsc and will
cause recent versions of osmo-bsc to crash. Lets remove this logging
categories from the config file now.
Change-Id: Idd85318abe3fc982909c11115c886835a3d8cd37
The file was modifiedosmo-bsc-latest/osmo-bsc.cfg