From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [RFC][PATCH] rootfs: Retry downloads 3 times
Date: Thu, 7 May 2020 20:13:57 +0200 [thread overview]
Message-ID: <20200507201357.5d24f91b@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <1d96541b-1263-773c-d340-35b0c73cb257@siemens.com>
The idea is good but the patch is incomplete.
To find all places where we download you might want to look at bitbake
fetchers in general - do they have a retry count?
Is there a variable controlling that?
After that look at all debian downloaders. You will find them when
looking for "download-only", "apt-get update" any maybe more. They
should use the central bitbake count or switch if available.
Your patch found one of many "download-only" and ignores bitbake. Might
be the most likely ... but we should try to be consistent.
Henning
Am Thu, 7 May 2020 16:36:18 +0200
schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Avoids failing a complete rootfs installation in case of a short
> hick-up.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>
> Does something like this make sense? Do we have more places?
> We have a retry of 2 on wget bitbake fetches, e.g. (via
> FETCHCMD_wget).
>
> meta/classes/rootfs.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/rootfs.bbclass b/meta/classes/rootfs.bbclass
> index 806e824c..afec1cbc 100644
> --- a/meta/classes/rootfs.bbclass
> +++ b/meta/classes/rootfs.bbclass
> @@ -123,7 +123,7 @@ rootfs_install_pkgs_download[weight] = "600"
> rootfs_install_pkgs_download[isar-apt-lock] = "release-after"
> rootfs_install_pkgs_download() {
> sudo -E chroot '${ROOTFSDIR}' \
> - /usr/bin/apt-get ${ROOTFS_APT_ARGS} --download-only
> ${ROOTFS_PACKAGES}
> + /usr/bin/apt-get ${ROOTFS_APT_ARGS} -o Acquire::Retries=3
> --download-only ${ROOTFS_PACKAGES} }
>
> ROOTFS_INSTALL_COMMAND_BEFORE_EXPORT ??= ""
next prev parent reply other threads:[~2020-05-07 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 14:36 Jan Kiszka
2020-05-07 18:13 ` Henning Schild [this message]
2020-05-08 5:57 ` Jan Kiszka
2020-05-08 7:07 ` Henning Schild
2020-05-25 14:10 ` Baurzhan Ismagulov
2020-05-25 14:13 ` Jan Kiszka
2020-05-25 14:30 ` Baurzhan Ismagulov
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=20200507201357.5d24f91b@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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