mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [PATCH v2] drm/ci: use shallow clone to avoid timeouts
@ 2025-02-28 15:12 Vignesh Raman
  2025-03-10  8:25 ` Daniel Stone
  0 siblings, 1 reply; 3+ messages in thread
From: Vignesh Raman @ 2025-02-28 15:12 UTC (permalink / raw)
  To: dri-devel
  Cc: daniels, helen.fornazier, airlied, simona.vetter, robdclark,
	dmitry.baryshkov, maarten.lankhorst, mripard, tzimmermann,
	guilherme.gallo, sergi.blanch.torne, valentine.burley,
	linux-kernel

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 50 to speed up cloning and avoid
build failures due to timeouts when fetching the full repository.

Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>
---

v2:
  - Set GIT_DEPTH to 50 to allow the check-patch job to pass

---
 drivers/gpu/drm/ci/gitlab-ci.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/gpu/drm/ci/gitlab-ci.yml b/drivers/gpu/drm/ci/gitlab-ci.yml
index f4e324e156db..3ba50fcd6f15 100644
--- a/drivers/gpu/drm/ci/gitlab-ci.yml
+++ b/drivers/gpu/drm/ci/gitlab-ci.yml
@@ -40,6 +40,8 @@ variables:
   ARTIFACTS_BASE_URL: https://${CI_PROJECT_ROOT_NAMESPACE}.${CI_PAGES_DOMAIN}/-/${CI_PROJECT_NAME}/-/jobs/${CI_JOB_ID}/artifacts
   # Python scripts for structured logger
   PYTHONPATH: "$PYTHONPATH:$CI_PROJECT_DIR/install"
+  # Set to 0 to disable shallow cloning
+  GIT_DEPTH: 50
 
 
 default:
-- 
2.47.2


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH v2] drm/ci: use shallow clone to avoid timeouts
  2025-02-28 15:12 [PATCH v2] drm/ci: use shallow clone to avoid timeouts Vignesh Raman
@ 2025-03-10  8:25 ` Daniel Stone
  2025-03-11  6:41   ` Vignesh Raman
  0 siblings, 1 reply; 3+ messages in thread
From: Daniel Stone @ 2025-03-10  8:25 UTC (permalink / raw)
  To: Vignesh Raman
  Cc: dri-devel, daniels, helen.fornazier, airlied, simona.vetter,
	robdclark, dmitry.baryshkov, maarten.lankhorst, mripard,
	tzimmermann, guilherme.gallo, sergi.blanch.torne,
	valentine.burley, linux-kernel

Hi Vignesh,

On Fri, 28 Feb 2025 at 15:12, Vignesh Raman <vignesh.raman@collabora.com> wrote:
> 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 50 to speed up cloning and avoid
> build failures due to timeouts when fetching the full repository.
>
> Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>
> ---
>
> v2:
>   - Set GIT_DEPTH to 50 to allow the check-patch job to pass

This sounds a bit fragile to me. Perhaps we need to make the
check-patch job instead specifically detect that it is missing history
and unshallow the history a bit more?

Cheers,
Daniel

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH v2] drm/ci: use shallow clone to avoid timeouts
  2025-03-10  8:25 ` Daniel Stone
@ 2025-03-11  6:41   ` Vignesh Raman
  0 siblings, 0 replies; 3+ messages in thread
From: Vignesh Raman @ 2025-03-11  6:41 UTC (permalink / raw)
  To: Daniel Stone
  Cc: dri-devel, daniels, helen.fornazier, airlied, simona.vetter,
	robdclark, dmitry.baryshkov, maarten.lankhorst, mripard,
	tzimmermann, guilherme.gallo, sergi.blanch.torne,
	valentine.burley, linux-kernel

Hi Daniel,

On 10/03/25 13:55, Daniel Stone wrote:
> Hi Vignesh,
> 
> On Fri, 28 Feb 2025 at 15:12, Vignesh Raman <vignesh.raman@collabora.com> wrote:
>> 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 50 to speed up cloning and avoid
>> build failures due to timeouts when fetching the full repository.
>>
>> Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>
>> ---
>>
>> v2:
>>    - Set GIT_DEPTH to 50 to allow the check-patch job to pass
> 
> This sounds a bit fragile to me. Perhaps we need to make the
> check-patch job instead specifically detect that it is missing history
> and unshallow the history a bit more?

Yes, we could do that. The check-patch job timeout is 1h (from gitlab 
project settings) and we can unshallow git history. I will send a
v3 after testing.

Regards,
Vignesh

> 
> Cheers,
> Daniel


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-03-11  6:42 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-02-28 15:12 [PATCH v2] drm/ci: use shallow clone to avoid timeouts Vignesh Raman
2025-03-10  8:25 ` Daniel Stone
2025-03-11  6:41   ` Vignesh Raman

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®