[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPj87rOT36e3TwZwk8uGUNpSz0kGB_XUY2gbCvGYYy2Xguqv5A@mail.gmail.com>
Date: Mon, 10 Mar 2025 08:25:53 +0000
From: Daniel Stone <daniel@...ishbar.org>
To: Vignesh Raman <vignesh.raman@...labora.com>
Cc: dri-devel@...ts.freedesktop.org, daniels@...labora.com,
helen.fornazier@...il.com, airlied@...il.com, simona.vetter@...ll.ch,
robdclark@...il.com, dmitry.baryshkov@...aro.org,
maarten.lankhorst@...ux.intel.com, mripard@...nel.org, tzimmermann@...e.de,
guilherme.gallo@...labora.com, sergi.blanch.torne@...labora.com,
valentine.burley@...labora.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] drm/ci: use shallow clone to avoid timeouts
Hi Vignesh,
On Fri, 28 Feb 2025 at 15:12, Vignesh Raman <vignesh.raman@...labora.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@...labora.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
Powered by blists - more mailing lists