Bug #3070
closedBSC_Tests.ttcn fails on all tests since 2018-03-13
100%
Description
For some reason, BSC_Tests.ttcn fails on all tests with "ERROR" since 2018-03-13, see e.g. https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bsc-test/109/
I've tracked the problem down to some C++ crash with backtrace in the generated C++ decoder for CtrlMessage upon receiving the CTRL response "GET_REPLY 290783505 bts.0.oml-connection-state degraded" from OsmoBSC.
The smallest test case to reproduce it is:
testcase TC_ctrldec() runs on test_CT {
var charstring inp := "GET_REPLY 290783505 bts.0.oml-connection-state degraded";
var CtrlMessage cmsg := dec_CtrlMessage(inp);
log(cmsg);
}
What's odd is that I cannot find any changes to the CTRL ttcn3 code in our repository (nor the IPA_Emulation.ttcnpp underneath), nor the libosmoctrl code during that timeframe at all.
The same code builds fine on TITAN 6.3.1 on Debian unstable.
In the past we've already had to work-around TITAN 6.1.0 bugs for things that were working perfectly fine in later releases like 6.2.0, 6.3.0 or 6.3.1. Upstream TITAN also has made it very clear that they strongly recommend running the latest release and they won't support anything else.
Updated by laforge about 6 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
As a result, I've built the TITAN 6.3.1 package from Debian unstable on Debian 9.0 using OBS. It's part of the network:osmocom:latest builds.
The debian-stretch-titan dockerfile has been adjusted to use the package from the network:osmocom:latest feed, rather than the package included with debian 9.0
The resulting build was working fine on my laptop (using the docker containers), and after pushing to master, it seems that the builds on jenkins now also work again: https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bsc-test/113
It sort-of sucks to not know what actually caused the bug, but rather than debuggin old TITAN C++ sources I think we should focus on fixing bugs in our own code.
As a result, though, you should switch to use TITAN 6.3.1, e.g. from the network:osmocom:latest feed, or from any other source. Sorry for that :/
