From: Vignesh Raman <vignesh.raman@collabora.com>
To: Daniel Stone <daniel@fooishbar.org>
Cc: dri-devel@lists.freedesktop.org, daniels@collabora.com,
helen.fornazier@gmail.com, airlied@gmail.com,
simona.vetter@ffwll.ch, robdclark@gmail.com,
dmitry.baryshkov@linaro.org, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de,
guilherme.gallo@collabora.com, sergi.blanch.torne@collabora.com,
valentine.burley@collabora.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm/ci: use shallow clone to avoid timeouts
Date: Tue, 11 Mar 2025 12:11:56 +0530 [thread overview]
Message-ID: <ad38518b-e335-4006-a04c-e15a6ef21694@collabora.com> (raw)
In-Reply-To: <CAPj87rOT36e3TwZwk8uGUNpSz0kGB_XUY2gbCvGYYy2Xguqv5A@mail.gmail.com>
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
prev parent reply other threads:[~2025-03-11 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 15:12 Vignesh Raman
2025-03-10 8:25 ` Daniel Stone
2025-03-11 6:41 ` Vignesh Raman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ad38518b-e335-4006-a04c-e15a6ef21694@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=daniel@fooishbar.org \
--cc=daniels@collabora.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=guilherme.gallo@collabora.com \
--cc=helen.fornazier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robdclark@gmail.com \
--cc=sergi.blanch.torne@collabora.com \
--cc=simona.vetter@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=valentine.burley@collabora.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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®