Project

General

Profile

Actions

Bug #4789

closed

no gerrit verifications on a 32bit architecture

Added by laforge over 3 years ago. Updated 10 months ago.

Status:
Closed
Priority:
Low
Assignee:
Target version:
-
Start date:
10/09/2020
Due date:
% Done:

0%

Spec Reference:

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

Related to libosmocore - Bug #4786: bssmap_le + bsslap tests compiler warning on i386Resolvedlaforge10/09/2020

Actions
Related to libosmocore - Bug #4787: libosmocore test suite failures on i386Resolvedlaforge10/09/2020

Actions
Has duplicate libosmocore - Feature #4727: Add more distro/platform/archs to jenkins CIFeedbacklaforge08/25/2020

Actions
Actions #1

Updated by laforge over 3 years ago

  • Related to Bug #4786: bssmap_le + bsslap tests compiler warning on i386 added
Actions #2

Updated by laforge over 3 years ago

  • Related to Bug #4787: libosmocore test suite failures on i386 added
Actions #3

Updated by laforge about 3 years ago

  • Assignee set to osmith
Actions #4

Updated by osmith over 2 years 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?
Actions #5

Updated by laforge over 1 year ago

  • Priority changed from High to Low

i guess this ticket might have been why there was an i586 executor on gtp0, which we just decommissioned?

osmith wrote in #note-4:

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?

I think gerrit verifications on 32bit would create a bit too much additional load. But master builds might be a good compromise. We'd see a problem at least after a 32bit-breaking change was merged.

Actions #6

Updated by osmith 10 months ago

  • Status changed from New to Closed

Very similar issue to #4727 where I just replied. Closing as duplicate.

Actions #7

Updated by osmith 10 months ago

  • Has duplicate Feature #4727: Add more distro/platform/archs to jenkins CI added
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)