Bug #4710
closed
osmo_sockaddr gtphub jenkins fallout
Added by laforge almost 4 years ago.
Updated almost 4 years ago.
Description
The jenkins job that tests the build of old applications against current libraries in 'master' is failing:
https://jenkins.osmocom.org/jenkins/job/Osmocom-build-tags-against-master/536/console
This is not unexpected. However, the job needs to be modified to pass again, ideally by
- just disabling the gtphub (applying some patch before build), or
- by tagging patch releases for all the tested application versions that cherry-pick the struct rename patch (1.5.0, 1.6.0, 1.6.1)
Simply not testing builds of osmo-sgsn against current master libraries is not an option.
1.6.2 worked, the 1.5.1 fails to build. I'm not going to investigate this further; lynxis, please take care of this.
- Status changed from New to In Progress
- % Done changed from 0 to 50
The build 1.5.1 fails because of the python2 and python3 migration. The build check on the jenkins fails, because the missing python package osmopy.obscvty.
It's only installed for python3 but not python3.
I'm installing the (old) package as python2.
- Status changed from In Progress to Feedback
- % Done changed from 50 to 70
- Status changed from Feedback to In Progress
- Status changed from In Progress to Feedback
- Status changed from Feedback to Closed
- % Done changed from 70 to 100
Also available in: Atom
PDF