Bug #4710
closedosmo_sockaddr gtphub jenkins fallout
100%
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
- 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.
Updated by laforge over 2 years ago
For 1.6.1 I am tagging a 1.6.2: https://gerrit.osmocom.org/c/osmo-sgsn/+/19614
Updated by laforge over 2 years ago
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.
Updated by lynxis over 2 years ago
- % 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.
Updated by lynxis over 2 years ago
waiting for review of https://gerrit.osmocom.org/c/osmo-ci/+/19661 to fix the jenkins build failures.
Updated by lynxis over 2 years ago
- Status changed from In Progress to Feedback
- % Done changed from 50 to 70
Updated by lynxis over 2 years ago
- Status changed from In Progress to Feedback
The gerrit patches aren't checked by the node itself, it's checked inside docker. even the jenkins nodes had the osmocom-python-tests installed under /usr/local.
Waiting for review another patch:
https://gerrit.osmocom.org/c/docker-playground/+/19663
Updated by lynxis over 2 years ago
- Status changed from Feedback to Closed
- % Done changed from 70 to 100
