Bug #2419
closedRecent AoIP builds failing on osmo-gsm-tester
0%
Description
Jenkins job building trials for osmo-msc (used in AoIP verison of tests, https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_build-osmo-msc/) looks to be configured to be triggered only by manual means, I guess that's due to being in development on the aoip branch.
This means osmo-gsm-tester is testing AoIP code not up to date, but from more than 1 month ago.
I recently build a complete trial of software using https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_manual-build-all/, which built last revision of aoip branch. Running it with the job https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_manual-run-all/ showed there are a lot of issues on that new revision.
To start with, it seems there is some new osmo-bsc config which is now mandatory and we don't have that set up. See https://git.osmocom.org/osmo-gsm-tester/commit/?h=point-code&id=0411af76c902f8556daaef0243e9140a1854d362 . After fixing that however, there seems to be other more deep issues which need to be solved.
Related issues
