From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [RFC][PATCH] rootfs: Retry downloads 3 times
Date: Mon, 25 May 2020 16:10:59 +0200 [thread overview]
Message-ID: <20200525141059.4nyeeof7jxkypqum@yssyq.m.ilbers.de> (raw)
In-Reply-To: <1d96541b-1263-773c-d340-35b0c73cb257@siemens.com>
On Thu, May 07, 2020 at 04:36:18PM +0200, Jan Kiszka wrote:
> Avoids failing a complete rootfs installation in case of a short
> hick-up.
...
> 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).
To address the questions raised in the thread, I think a small improvement now
is a good thing. I also think it's worth to gradually fix all relevant places
and unify the retry handling.
I'd like to apply this as is. Jan, you are not planning an update for this, are
you?
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2020-05-25 14:11 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
2020-05-08 5:57 ` Jan Kiszka
2020-05-08 7:07 ` Henning Schild
2020-05-25 14:10 ` Baurzhan Ismagulov [this message]
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=20200525141059.4nyeeof7jxkypqum@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.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