linux-kernel - Re: [PATCH v2] drm/ci: use shallow clone to avoid timeouts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ad38518b-e335-4006-a04c-e15a6ef21694@collabora.com>
Date: Tue, 11 Mar 2025 12:11:56 +0530
From: Vignesh Raman <vignesh.raman@...labora.com>
To: Daniel Stone <daniel@...ishbar.org>
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 Daniel,

On 10/03/25 13:55, Daniel Stone wrote:
> 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?

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