aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlex Bennée <alex.bennee@linaro.org>2025-06-27 12:24:57 +0100
committerAlex Bennée <alex.bennee@linaro.org>2025-07-02 09:56:37 +0100
commit6af9f88fff5baea33469d52b94c7e64bd596713e (patch)
tree397b1455d5b2ab1758d3001bde2e3d672eab7a3b
parent6138e72b7e33e0240ee955a2754dd038ee99494d (diff)
downloadqemu-6af9f88fff5baea33469d52b94c7e64bd596713e.zip
qemu-6af9f88fff5baea33469d52b94c7e64bd596713e.tar.gz
qemu-6af9f88fff5baea33469d52b94c7e64bd596713e.tar.bz2
gitlab: mark s390x-system to allow failures
The system tests (usually qos-test or migration-test) prove to be very susceptible on the s390x runners. Although we have boosted memory and virtual CPUs on the runners problems persist. For now mark test as allow_failure so the its clear on the CI UI when checking test results. Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Message-ID: <20250627112512.1880708-2-alex.bennee@linaro.org>
-rw-r--r--.gitlab-ci.d/custom-runners/ubuntu-22.04-s390x.yml2
1 files changed, 2 insertions, 0 deletions
diff --git a/.gitlab-ci.d/custom-runners/ubuntu-22.04-s390x.yml b/.gitlab-ci.d/custom-runners/ubuntu-22.04-s390x.yml
index ca374ac..e62ff17 100644
--- a/.gitlab-ci.d/custom-runners/ubuntu-22.04-s390x.yml
+++ b/.gitlab-ci.d/custom-runners/ubuntu-22.04-s390x.yml
@@ -31,7 +31,9 @@ ubuntu-22.04-s390x-all-system:
timeout: 75m
rules:
- if: '$CI_PROJECT_NAMESPACE == "qemu-project" && $CI_COMMIT_BRANCH =~ /^staging/'
+ allow_failure: true
- if: "$S390X_RUNNER_AVAILABLE"
+ allow_failure: true
script:
- mkdir build
- cd build