Bug #3767
closedMost ttcn3-*-test-latest jenkins jobs are failing
100%
Description
New Osmocom version were released yesterday, and we expected that the -latest jobs would finally reach the same state as the master ones (the ones without a suffix).
However, most tests are still failing for various reasons:
See https://jenkins.osmocom.org/jenkins/view/TTCN3/
This was partially caused by updating eclipse-titan from 6.3.1 to 6.5.0 in the binary package repository, which then meant that our tests were not building anymore (they couldn't find TTCN3.hh anymore). So the testing docker containers were not building anymore, and a following bug in jenkins_common.sh caused the jobs not to abort there, but to continue with the last image that it was able to build (patch to fix that submitted here). The eclipse-titan update was reverted here and now the docker container builds again.
But the problem is not resolved yet, ttcn3-bts-test-latest for example is still failing.
I think daniel mentioned that he saw a "command not found" in the log? I can't find it though.
I will look more into this tomorrow.
Checklist
- fix ttcn3-hlr-test-latest in my branch
- fix ttcn3-msc-test-latest in my branch
- fix ttcn3-sgsn-test-latest in my branch
- fix ttcn3-sip-test-latest in my branch
- get changes merged into master
- fix ttcn3-bts-test-latest in my branch
Related issues