From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Tomasz Dziendzielski <tomasz.dziendzielski@gmail.com>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
Michal Sieron <michalwsieron@gmail.com>,
bitbake-devel@lists.openembedded.org,
Mateusz Marciniec <mateuszmar2@gmail.com>
Subject: Re: [bitbake-devel] [PATCH] bitbake: Add task timeout support
Date: Thu, 25 May 2023 15:57:12 +0300 [thread overview]
Message-ID: <ZG9bKB8yLRMKqZYT@nuoska> (raw)
In-Reply-To: <CAJkqNs33qZDkgJGgFh5a9CZ7wZFZqvVGPDmZnKruP5g_7MRBNw@mail.gmail.com>
Hi,
On Thu, May 25, 2023 at 02:13:10PM +0200, Tomasz Dziendzielski wrote:
> >Yocto has a download cache mechanism, so you should not have to fetch
> >more than once. Are you throwing away that cache between builds?
>
> Do you mean the DL_DIR or something else as cache mechanism? We do keep
> DL_DIR between builds, but we're talking about cases where there was a
> change in the repository.
>
> >the actual problem is slow gerrit/artifactory instances, not
> >stuck fetch tasks
> Totally agree, but we're not able to fix the slow gerrit/artifactory in a
> short term.
>
> >The idea of 'retrying' the fetch
> Well, it's not like I'm saying this as a solution, usually we just
> disable jobs until the slowness is gone. But isn't that what we already do
> with wget in bitbake?
> "wget -t 2 -T 30" from bitbake/lib/bb/fetch2/wget.py, where -t is tries,
> and -T is timeout
> Problem is that we get the slowness for git repositories and git does not
> support such a thing.
git uses curl, can't we shorten the timeouts or even add retries there? Maybe even
specific ones for the lfs support?
I've also seen a lot of problematic artifactory and gerrit instances, in addition
to maven, npm etc...
Cheers,
-Mikko
next prev parent reply other threads:[~2023-05-25 12:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 10:21 [PATCH] bitbake: Add task timeout support Michal Sieron
2023-05-25 10:44 ` [bitbake-devel] " Mikko Rapeli
2023-05-25 10:59 ` Alexander Kanavin
2023-05-25 11:44 ` Tomasz Dziendzielski
2023-05-25 12:00 ` Alexander Kanavin
2023-05-25 12:13 ` Tomasz Dziendzielski
2023-05-25 12:21 ` Alexander Kanavin
2023-05-25 12:35 ` Tomasz Dziendzielski
2023-05-25 12:57 ` Mikko Rapeli [this message]
2023-06-05 11:46 ` Michal Sieron
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=ZG9bKB8yLRMKqZYT@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=alex.kanavin@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=mateuszmar2@gmail.com \
--cc=michalwsieron@gmail.com \
--cc=tomasz.dziendzielski@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.