Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jacob Kroon <jacob.kroon@gmail.com>
To: Ross Burton <ross@burtonini.com>, Pavel Zhukov <pavel@zhukoff.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] sanity.class: Add possibility to configure networking check
Date: Fri, 11 Feb 2022 12:23:03 +0100	[thread overview]
Message-ID: <be3113b8-81a1-ca3a-32d2-4fa6783bfec2@gmail.com> (raw)
In-Reply-To: <CAAnfSTsvaGZ2khtFLNdkqbMRK_Yx_CmOLtSj_Jt4PSJZOb970g@mail.gmail.com>

On 2/11/22 12:18, Ross Burton wrote:
> On Fri, 11 Feb 2022 at 08:44, Pavel Zhukov <pavel@zhukoff.net> wrote:
>> +        for uri in test_uris:
>> +            try:
>> +                if check_all:
>> +                    fetcher = bb.fetch2.Fetch(test_uris, data)
>> +                else:
>> +                    fetcher = bb.fetch2.Fetch([uri], data)
>> +                fetcher.checkstatus()
>> +                return retval
> 
> This seems like it's overcomplicating things to me.  example.com was
> having uptime issues, and we can change it to www.yoctoproject.org so
> that we know in advance of expected downtime, and have direct contact
> with the people responsible for keeping it up. So let's just change
> the URL to www.yoctoproject.org instead of adding more variables and
> non-trivial logic.
> 

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.

Jacob


  reply	other threads:[~2022-02-11 11:23 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 [this message]
2022-02-11 11:39     ` Ross Burton
2022-02-11 12:08       ` Jacob Kroon
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=be3113b8-81a1-ca3a-32d2-4fa6783bfec2@gmail.com \
    --to=jacob.kroon@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pavel@zhukoff.net \
    --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