gitlab: let rawhide container builds fail

The nature of Fedora rawhide means that it will inevitably have failures
periodically. Currently it is failing to even update packages due to
glibc switching to use of clone3 syscall, which is mistakenly blocked by
seccomp in container runtimes using EPERM instead of ENOSYS.

When we fail to build the rawhide containers, it is quite likely that we
still have the previous build available in the gitlab registry, so it is
reasonable to allow the container job to fail and try the build job
anyway.

Ideally we would ignore the container build failure if-and-only-if the
previous container was build with the same list of packages. We don't
record the original dependency package list though, so that's not
currently possible.

Reviewed-by: Peter Krempa <pkrempa@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
This commit is contained in:
Daniel P. Berrangé 2021-07-26 10:35:41 +01:00
parent f513297bd4
commit 42f3ec7500

View File

@ -186,7 +186,7 @@ x64-fedora-34-container:
NAME: fedora-34 NAME: fedora-34
x64-fedora-rawhide-container: x64-fedora-rawhide-container:
extends: .container_job extends: .container_optional_job
variables: variables:
NAME: fedora-rawhide NAME: fedora-rawhide
@ -299,12 +299,12 @@ s390x-debian-sid-container:
NAME: debian-sid-cross-s390x NAME: debian-sid-cross-s390x
mingw32-fedora-rawhide-container: mingw32-fedora-rawhide-container:
extends: .container_job extends: .container_optional_job
variables: variables:
NAME: fedora-rawhide-cross-mingw32 NAME: fedora-rawhide-cross-mingw32
mingw64-fedora-rawhide-container: mingw64-fedora-rawhide-container:
extends: .container_job extends: .container_optional_job
variables: variables:
NAME: fedora-rawhide-cross-mingw64 NAME: fedora-rawhide-cross-mingw64