Bug #4789
openno gerrit verifications on a 32bit architecture
0%
Description
Most of our projects, particularly not libosmo*, only have gerrit build verification on amd64, but not on any 32bit architecture like i386 or armv7l.
This leads to 32bit compatibility issues slipping through the cracks and only showing up later in OBS builds, like seen with #4786 and #4787.
Let's add verification on 32bit. We need some i386 jenkins slaves (via ansible) and the associated jenkins job-builder voodoo.
I would go straight for debian10, despite the amd64 builds still being tested on debian9.
Related issues
Updated by laforge about 1 year ago
- Related to Bug #4786: bssmap_le + bsslap tests compiler warning on i386 added
Updated by laforge about 1 year ago
- Related to Bug #4787: libosmocore test suite failures on i386 added
Updated by osmith 6 months ago
Most of our projects, particularly not libosmo*, only have gerrit build verification on amd64, but not on any 32bit architecture like i386 or armv7l.
The raspberries run armv7l, 32-bit. In theory they can run aarch64 too, but IIRC some blobs weren't available for aarch64 initially and so raspbian is 32-bit. (Meanwhile it's possible to run them on aarch64 too, with other distros.) So all builds that run on the pis get built for 32 bit arm FWIW. But still, most projects don't get tested on 32 bit.
Let's add verification on 32bit. We need some i386 jenkins slaves (via ansible) and the associated jenkins job-builder voodoo.
On which hosts should the jenkins slaves be set up?
How should this be implemented?
- should gerrit verifications run additionally on 32-bit arches?
- should master builds run additionally on 32-bit arches?
- or would you like to add the nodes and have randomly builds started either on 64 bit or 32 bit?
