[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6da17cd3-77f2-4bf4-86b8-296c2f295960@collabora.com>
Date: Fri, 28 Mar 2025 17:40:02 +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, guilherme.gallo@...labora.com,
sergi.blanch.torne@...labora.com, valentine.burley@...labora.com,
lumag@...nel.org, quic_abhinavk@...cinc.com, mripard@...nel.org,
maarten.lankhorst@...ux.intel.com, tzimmermann@...e.de,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 2/3] drm/ci: check-patch: unshallow repository before
fetching
Hi Daniel,
On 28/03/25 17:05, Daniel Stone wrote:
> Hi Vignesh,
>
> On Fri, 28 Mar 2025 at 11:03, Vignesh Raman <vignesh.raman@...labora.com> wrote:
>> Ensure the repository is not shallow before fetching branches in
>> check-patch job. This prevents issues where git merge-base fails
>> due to incomplete history. Set the timeout of check-patch job to 1h.
>
> Ouch - an hour is pretty brutal. Is there a way to unshallow only back
> to the merge base?
I set it to 1h, but the job is completed in ~15min for
https://gitlab.freedesktop.org/vigneshraman/linux/-/merge_requests/18
which has 486 commits.
I will check if we can unshallow only up to the merge base.
Regards,
Vignesh
>
> Cheers,
> Daniel
Powered by blists - more mailing lists