mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vignesh Raman <vignesh.raman@collabora.com>
To: dri-devel@lists.freedesktop.org
Cc: daniels@collabora.com, daniel@fooishbar.org,
	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,
	dmitry.baryshkov@oss.qualcomm.com, quic_abhinavk@quicinc.com,
	mripard@kernel.org, maarten.lankhorst@linux.intel.com,
	tzimmermann@suse.de, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] drm/ci: mesa uprev and python-artifacts fixes
Date: Wed, 14 May 2025 10:33:34 +0530	[thread overview]
Message-ID: <20250514050340.1418448-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. Set GIT_DEPTH to 10 to speed up cloning and avoid
build failures due to timeouts when fetching the full repository.

The current s3cp stopped working after the migration. Update to the
latest mesa and ci-templates to get s3cp working again and adapt to
recent changes in mesa-ci.

check-patch testing,
MR - https://gitlab.freedesktop.org/vigneshraman/linux/-/merge_requests/22
pipeline - https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1418294

mesa uprev testing,
pipeline - https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1418293

msm merge request,
https://gitlab.freedesktop.org/drm/msm/-/merge_requests/169
 
i915:cml jobs are stuck due to some issue with devices in the lava lab.

Vignesh Raman (2):
  drm/ci: python-artifacts: use shallow clone
  drm/ci: uprev mesa and ci-templates

 drivers/gpu/drm/ci/build-igt.sh   |  2 +-
 drivers/gpu/drm/ci/build.sh       |  6 ++--
 drivers/gpu/drm/ci/build.yml      | 10 +++++--
 drivers/gpu/drm/ci/container.yml  | 30 +++++--------------
 drivers/gpu/drm/ci/gitlab-ci.yml  | 50 +++++++++++++++++++++----------
 drivers/gpu/drm/ci/igt_runner.sh  |  1 +
 drivers/gpu/drm/ci/image-tags.yml | 20 +++++--------
 drivers/gpu/drm/ci/lava-submit.sh |  6 ++--
 drivers/gpu/drm/ci/test.yml       | 31 ++++++++++---------
 9 files changed, 80 insertions(+), 76 deletions(-)

-- 
2.47.2


             reply	other threads:[~2025-05-14  5:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-14  5:03 Vignesh Raman [this message]
2025-05-14  5:03 ` [PATCH v3 1/2] drm/ci: python-artifacts: use shallow clone Vignesh Raman
2025-05-14  5:03 ` [PATCH v3 2/2] drm/ci: uprev mesa and ci-templates Vignesh Raman
2025-05-19 10:37 ` [PATCH v3 0/2] drm/ci: mesa uprev and python-artifacts fixes Daniel Stone

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=20250514050340.1418448-1-vignesh.raman@collabora.com \
    --to=vignesh.raman@collabora.com \
    --cc=airlied@gmail.com \
    --cc=daniel@fooishbar.org \
    --cc=daniels@collabora.com \
    --cc=dmitry.baryshkov@oss.qualcomm.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®