summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
diff options
context:
space:
mode:
authorCarlos Garnacho <carlosg@gnome.org>2022-03-07 17:50:48 +0100
committerCarlos Garnacho <carlosg@gnome.org>2022-03-08 11:31:15 +0100
commit5b4410c791f056991d3ffec7cef15818cae8b169 (patch)
treee0069a54393d1020b76e4b1d59cdb2f9cabc3c3b /.gitlab-ci.yml
parent0a07d77d376b44c7ea95f97db7f9a0188e80638b (diff)
downloadtracker-5b4410c791f056991d3ffec7cef15818cae8b169.tar.gz
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.
Diffstat (limited to '.gitlab-ci.yml')
-rw-r--r--.gitlab-ci.yml5
1 files changed, 5 insertions, 0 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index ea1feb96a..668b62592 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: