From: Vignesh Raman <vignesh.raman@collabora.com>
To: dri-devel@lists.freedesktop.org
Cc: daniels@collabora.com, helen.fornazier@gmail.com,
airlied@gmail.com, simona.vetter@ffwll.ch, robdclark@gmail.com,
guilherme.gallo@collabora.com, sergi.blanch.torne@collabora.com,
valentine.burley@collabora.com, lumag@kernel.org,
quic_abhinavk@quicinc.com, mripard@kernel.org,
maarten.lankhorst@linux.intel.com, tzimmermann@suse.de,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/3] drm/ci: mesa uprev and python-artifacts/check-patch fixes
Date: Fri, 28 Mar 2025 16:32:30 +0530 [thread overview]
Message-ID: <20250328110239.993685-1-vignesh.raman@collabora.com> (raw)
The python-artifacts job has a timeout of 10 minutes, which causes
build failures as it was unable to clone the repository within the
specified limits. This patch sets GIT_DEPTH to 10 to speed up cloning
and avoid build failures due to timeouts when fetching the full
repository.
The check-patch job is also updated to ensure the repository is not
shallow before fetching branches. This prevents issues where git
merge-base fails due to incomplete history. Additionally, the timeout
for the check-patch job is set to 1 hour.
The current s3cp implementation does not work anymore after the migration.
Uprev mesa to adapt these changes. Also replace broken s3cp command with a
curl wrapper call in drm-ci.
check-patch testing,
MR - https://gitlab.freedesktop.org/vigneshraman/linux/-/merge_requests/18
pipeline - https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1391545
mesa uprev testing,
MR - https://gitlab.freedesktop.org/vigneshraman/linux/-/merge_requests/18
pipeline - https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1391440
Google farm is down, so the baremetal jobs failed.
i915:cml jobs are stuck due to some devices in the lab being under maintenance.
Vignesh Raman (3):
drm/ci: use shallow clone to avoid timeouts
drm/ci: check-patch: unshallow repository before fetching
drm/ci: uprev mesa
drivers/gpu/drm/ci/build-igt.sh | 2 +-
drivers/gpu/drm/ci/build.sh | 6 +++---
drivers/gpu/drm/ci/check-patch.py | 16 ++++++++++++----
drivers/gpu/drm/ci/gitlab-ci.yml | 8 ++++++--
drivers/gpu/drm/ci/image-tags.yml | 2 +-
drivers/gpu/drm/ci/lava-submit.sh | 2 +-
drivers/gpu/drm/ci/static-checks.yml | 1 +
7 files changed, 25 insertions(+), 12 deletions(-)
--
2.47.2
next reply other threads:[~2025-03-28 11:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 11:02 Vignesh Raman [this message]
2025-03-28 11:02 ` [PATCH v1 1/3] drm/ci: use shallow clone to avoid timeouts Vignesh Raman
2025-03-28 11:02 ` [PATCH v1 2/3] drm/ci: check-patch: unshallow repository before fetching Vignesh Raman
2025-03-28 11:35 ` Daniel Stone
2025-03-28 12:10 ` Vignesh Raman
2025-04-03 6:02 ` Vignesh Raman
2025-03-28 11:02 ` [PATCH v1 3/3] drm/ci: uprev mesa Vignesh Raman
2025-03-28 11:36 ` Daniel Stone
2025-03-28 11:59 ` Vignesh Raman
2025-04-03 5:59 ` Vignesh Raman
2025-04-29 18:21 ` Dmitry Baryshkov
2025-04-30 1:33 ` Vignesh Raman
2026-03-25 5:32 ` [PATCH v1 0/3] drm/ci: mesa uprev and python-artifacts/check-patch fixes Dmitry Baryshkov
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=20250328110239.993685-1-vignesh.raman@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=guilherme.gallo@collabora.com \
--cc=helen.fornazier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sergi.blanch.torne@collabora.com \
--cc=simona.vetter@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=valentine.burley@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®