[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231009004953.203576-9-helen.koike@collabora.com>
Date: Sun, 8 Oct 2023 21:49:53 -0300
From: Helen Koike <helen.koike@...labora.com>
To: Helen Koike <helen.koike@...labora.com>,
David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>
Cc: robdclark@...omium.org, dmitry.baryshkov@...aro.org,
vignesh.raman@...labora.com, sergi.blanch.torne@...labora.com,
guilherme.gallo@...labora.com, david.heidelberg@...labora.com,
quic_abhinavk@...cinc.com, quic_jesszhan@...cinc.com,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: [PATCH 8/9] drm/ci: do not automatically retry on error
Since the kernel doesn't use a bot like Mesa that requires tests to pass
in order to merge the patches, leave it to developers and/or maintainers
to manually retry.
Suggested-by: Rob Clark <robdclark@...omium.org>
Signed-off-by: Helen Koike <helen.koike@...labora.com>
---
drivers/gpu/drm/ci/gitlab-ci.yml | 14 --------------
1 file changed, 14 deletions(-)
diff --git a/drivers/gpu/drm/ci/gitlab-ci.yml b/drivers/gpu/drm/ci/gitlab-ci.yml
index 9326522823bb..6c5bf6fac697 100644
--- a/drivers/gpu/drm/ci/gitlab-ci.yml
+++ b/drivers/gpu/drm/ci/gitlab-ci.yml
@@ -55,20 +55,6 @@ default:
export CI_JOB_JWT="$(<${CI_JOB_JWT_FILE})" &&
rm "${CI_JOB_JWT_FILE}"
- # Retry when job fails.
- retry:
- max: 1
- # Ignore runner_unsupported, stale_schedule, archived_failure, or
- # unmet_prerequisites
- when:
- - api_failure
- - runner_system_failure
- - script_failure
- - job_execution_timeout
- - scheduler_failure
- - data_integrity_failure
- - unknown_failure
-
include:
- project: 'freedesktop/ci-templates'
ref: 16bc29078de5e0a067ff84a1a199a3760d3b3811
--
2.34.1
Powered by blists - more mailing lists