From: Jacob Kroon <jacob.kroon@gmail.com>
To: Ross Burton <ross@burtonini.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] sanity.class: Add possibility to configure networking check
Date: Fri, 11 Feb 2022 13:08:26 +0100 [thread overview]
Message-ID: <b8ff8c70-ddcd-5a31-ce40-53fe2f43d2b1@gmail.com> (raw)
In-Reply-To: <CAAnfSTt==tDAVW7DaGKKDwwJvwGbTQPw26-Oc2dDpeQf263Wsw@mail.gmail.com>
On 2/11/22 12:39, Ross Burton wrote:
> On Fri, 11 Feb 2022 at 11:23, Jacob Kroon <jacob.kroon@gmail.com> wrote:
>> I vote for removing the check altogether.
>>
>> As I understand it, the check was added in order to prevent
>> hard-to-interpret error messages when network failed. I can live with that.
>
> I think the check should remain, and example.com has served well for
> some time now (since 2016 in
> 423a2645377bff2cd7292e1dc9796eeb3595e937).
>
> We moved to example.com to speed up the check: the old tests were for
> two yoctoproject.org URLs and it downloads the entire page, so that
> took time.
>
> If we can get a minimal page added to yoctoproject.org that doesn't
> involve hitting WordPress, then we can own the URL and have fast
> responses.
>
I suppose if the intention is that the Yocto server will never ever be
down, the check is ok. But if it is ever going to need to go down
because of maintenance you will break bitbake builds for everyone in the
world, right ? Then I don't think users will be happy, even though the
downtime was planned and publicly announced on some website.
Jacob
next prev parent reply other threads:[~2022-02-11 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 8:44 [PATCH] sanity.class: Add possibility to configure networking check Pavel Zhukov
2022-02-11 11:18 ` [OE-core] " Ross Burton
2022-02-11 11:23 ` Jacob Kroon
2022-02-11 11:39 ` Ross Burton
2022-02-11 12:08 ` Jacob Kroon [this message]
2022-02-11 13:13 ` Richard Purdie
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=b8ff8c70-ddcd-5a31-ce40-53fe2f43d2b1@gmail.com \
--to=jacob.kroon@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross@burtonini.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