[PATCH v2] drm/ci: use shallow clone to avoid timeouts
Vignesh Raman
vignesh.raman at collabora.com
Tue Mar 11 06:41:56 UTC 2025
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 at 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 at 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
More information about the dri-devel
mailing list