mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helen Koike <helen.koike@collabora.com>
To: Helen Koike <helen.koike@collabora.com>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: robdclark@chromium.org, dmitry.baryshkov@linaro.org,
	vignesh.raman@collabora.com, sergi.blanch.torne@collabora.com,
	guilherme.gallo@collabora.com, david.heidelberg@collabora.com,
	quic_abhinavk@quicinc.com, quic_jesszhan@quicinc.com,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH 8/9] drm/ci: do not automatically retry on error
Date: Sun,  8 Oct 2023 21:49:53 -0300	[thread overview]
Message-ID: <20231009004953.203576-9-helen.koike@collabora.com> (raw)
In-Reply-To: <20231009004953.203576-1-helen.koike@collabora.com>

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@chromium.org>
Signed-off-by: Helen Koike <helen.koike@collabora.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


  parent reply	other threads:[~2023-10-09  0:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09  0:49 [PATCH 0/9] drm/ci: fixes and improvements Helen Koike
2023-10-09  0:49 ` [PATCH 1/9] drm/ci: uprev mesa version - fix container build Helen Koike
2023-10-11 18:52   ` David Heidelberg
2023-10-09  0:49 ` [PATCH 2/9] drm/ci: fix DEBIAN_ARCH and get amdgpu probing Helen Koike
2023-10-09  0:49 ` [PATCH 3/9] drm/ci: add helper script update-xfails.py Helen Koike
2023-10-10  7:50   ` Vignesh Raman
2023-10-09  0:49 ` [PATCH 4/9] drm/ci: uprev IGT and make sure core_getversion is run Helen Koike
2023-10-09  0:49 ` [PATCH 5/9] drm/ci: clean up xfails (specially flakes list) Helen Koike
2023-10-09  0:49 ` [PATCH 6/9] drm/ci: adjust the number of shards Helen Koike
2023-10-09  0:49 ` [PATCH 7/9] drm/ci: export kernel config Helen Koike
2023-10-09  9:30   ` Dmitry Baryshkov
2023-10-09  0:49 ` Helen Koike [this message]
2023-10-09  0:49 ` [PATCH 9/9] drm/ci: docs: add step about how to request privileges Helen Koike
2023-10-11 18:54 ` [PATCH 0/9] drm/ci: fixes and improvements David Heidelberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231009004953.203576-9-helen.koike@collabora.com \
    --to=helen.koike@collabora.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=david.heidelberg@collabora.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=guilherme.gallo@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=quic_jesszhan@quicinc.com \
    --cc=robdclark@chromium.org \
    --cc=sergi.blanch.torne@collabora.com \
    --cc=vignesh.raman@collabora.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®