Unify gh_strfmt_errors job and gh_32-bit-build-smoke jobs

[mykaul]

What's the difference between gh_strfmt_errors job and gh_32-bit-build-smoke jobs? They both use Fedora (cool), 32bit (OK), F32 (old! need to update!), both compile Gluster , EC dynamic support : x64 sse avx (which seems to be a machine specific setting?) the other 'none', one with gNFS, the other without, Python 3.8 vs 3.9 (does it matter?), one with LTO, the other without (not sure why), but essentially produce very similar build? Can't we just unify them and save us some cycles?

[mscherer]

gh_32-bit-build-smoke test the build on 32 bits (on a F33 chroot). If the build fail for any reason, it fail.

gh_strfmt_errors build on x86-64 and check for specific warning and turn them to error.

https://github.com/gluster/build-jobs/blob/main/build-gluster-org/scripts/strfmt_errors.sh vs https://github.com/gluster/build-jobs/blob/main/build-gluster-org/scripts/32-bit-build-smoke.sh

So more refactoring could be done, but they are quite different build jobs.

As for the F32, it should be updated, but since newer Fedora drop i386, we are limited in our options.

[mykaul]

The strfmt is on 64bit?

Setting status of 7bac25b47af834cd2bea4ea56097743b64e970de to PENDING with url https://build.gluster.org/job/gh_strfmt_errors/2356/ and message: 'Running: strfmt errors in a 32 build'
Using context: Testing: strfmt errors in a 32 build
Building remotely on builder-f32-2.int.rht.gluster.org (fedora32 fedora32-cage) in workspace /home/jenkins/root/workspace/gh_strfmt_errors

(From https://build.gluster.org/job/gh_strfmt_errors/2356/consoleFull )

[mscherer]

Mhh, indeed, that's build on a F33 chroot for i686.

[mscherer]

To be fair, I am not sure if 32 bits is still relevant. Neither Fedora nor RHEL support t, and I think the way forward would be to have a 32 bits builder on Debian or Ubuntu, so maybe we should just drop theses 2 jobs and replace one with a supported updated 32 bits distros.

[mykaul]

I agree, I think it should also be on ARM.

[mscherer]

ARM, I guess that's aarch64, that's doable. AWS has graviton instance, the biggest issue will be on our side I guess.

ARM 32 bits, well, I have plenty of board lying around, but I wouldn't recommend that for CI :)

[mscherer]

The lack of aarch64 image on https://alt.fedoraproject.org/cloud/ is for now a blocker , let's see if there is F34 images at least.

[mykaul]

https://cloud.centos.org/centos/9-stream/aarch64/images/ perhaps?

[mscherer]

Our automation use uploaded AMI, we can't use a external image for now (should be doable if there is no others choice) So I went to web archive and got the old AMI for F34, and opened a bug for Fedora website team: https://pagure.io/fedora-websites/issue/1135

So I added https://github.com/gluster/gluster.org_ansible_configuration/commit/39378c202652c4dd29e8d84a62a8bce9c4b72dd4 and the builder is being installed.