[tracker/wip/carlosg/ci-pipelines: 1/2] ci: Work around rawhide failures by using crun runners
- From: Carlos Garnacho <carlosg src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [tracker/wip/carlosg/ci-pipelines: 1/2] ci: Work around rawhide failures by using crun runners
- Date: Mon, 7 Mar 2022 17:58:36 +0000 (UTC)
commit 804043d00126ecd2496fc3db4b70669ee2a4607d
Author: Carlos Garnacho <carlosg gnome org>
Date: Mon Mar 7 17:50:48 2022 +0100
ci: Work around rawhide failures by using crun runners
With a combination of recent glib, and old runc/seccomp in the
runners, we run into the error messages described at:
https://gitlab.gnome.org/Infrastructure/GitLab/-/issues/545
So far, the advised workaround is to use the `crun` tag to use
runners that don't run that combination of software. Add this
specifically for the rawhide test job.
.gitlab-ci.yml | 5 +++++
1 file changed, 5 insertions(+)
---
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 0e318bf86..71b332ada 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -330,6 +330,11 @@ test-fedora-rawhide@x86_64:
needs:
- build-fedora-rawhide@x86_64
allow_failure: true
+ tags:
+ # There is a mismatch between syscalls and seccomp rules in
+ # some runners, using `crun` is advised in the mean time, see
+ # https://gitlab.gnome.org/Infrastructure/GitLab/-/issues/545
+ - crun
<<: *test
test-fedora@aarch64:
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]