All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: poky <poky@lists.yoctoproject.org>
Subject: Default network connectivity sanity tests
Date: Thu, 13 Sep 2012 18:50:49 +0100	[thread overview]
Message-ID: <1347558649.11710.114.camel@ted> (raw)

Currently the poky distro config tests for three different kinds of
network connectivity:

# The CONNECTIVITY_CHECK_URI's are used to test whether we can succesfully
# fetch from the network (and warn you if not). To disable the test set
# the variable to be empty.
CONNECTIVITY_CHECK_URIS ?= "git://git.yoctoproject.org/yocto-firewall-test;protocol=git;rev=HEAD \
                          https://eula-downloads.yoctoproject.org/index.php \
                          http://bugzilla.yoctoproject.org/report.cgi"

So this tests http, https and git. The theory goes that the project
mirrors should be a) preferred and b) be up to date in most cases so
that you'd only ever usually need http:// to run a build successfully.

There are some "windows of opportunity" when building from master where
this might not be true, for example, a kernel update has just been
pushed and the mirrors have not updated to the latest code. In this
scenario, bitbake would pull the mirror tarball, then updated it using
the git protocol.

I'm getting continued complaints that git is horrible to proxy behind
firewalls and this check continues to cause pain for people when in fact
the builds would probably work. These complains go so far as to say
we're ruining the reputation of the project by having this as people
leave after an initial bad experience. I'm reaching the point where I
become tempted to remove it.

Opinions?

One other option would be to remove it on release branches. Those should
be more stable and therefore shouldn't need this kind of check...

Cheers,

Richard




             reply	other threads:[~2012-09-13 17:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13 17:50 Richard Purdie [this message]
2012-09-14 17:01 ` Default network connectivity sanity tests Trevor Woerner

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=1347558649.11710.114.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=poky@lists.yoctoproject.org \
    /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.