From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 0/2] Sanity testing network connectivity
Date: Fri, 17 Jun 2011 20:09:03 -0700 [thread overview]
Message-ID: <1308366548.2245.14.camel@scimitar> (raw)
In-Reply-To: <cover.1308365562.git.josh@linux.intel.com>
On Fri, 2011-06-17 at 20:04 -0700, Joshua Lock wrote:
> In response to a Yocto Bugzilla request[1] I've written a sanity test to check
> whether BitBake is able to fecth from http, https and git sources. The idea
> being that if the user is behing a proxy and this test fails we can more easily
> help them diagnose and fix their problem.
>
> I've built on the existing infrastructure for less frequent sanity tests so
> whilst this test is reasonably heavy it will only run when TMPDIR changes
> (usually first run?). Further I added a variable to disable just this sanity
> check. People shipping offline installs to customers should just be able to
> set the variable in their shipped configuration and not worry about this
> sanity check irritating people.
>
> The error message points to a wiki page[2] which is pretty vanilla right now
> but the intention would be to flesh it out with guidance on common proxy/nat/etc
> issues.
I cunningly forgot the url's I referenced. Friday evening, sorry.
1. http://bugzilla.pokylinux.org/show_bug.cgi?id=933
2. https://wiki.yoctoproject.org/wiki/Connectivity_Troubleshooting
Joshua
--
Joshua Lock
Yocto Build System Monkey
Intel Open Source Technology Centre
prev parent reply other threads:[~2011-06-18 3:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 3:04 [RFC PATCH 0/2] Sanity testing network connectivity Joshua Lock
2011-06-18 3:04 ` [RFC PATCH 1/2] sanity.bbclass: pass the data object to the less frequent test harnesses Joshua Lock
2011-06-18 3:04 ` [RFC PATCH 2/2] sanity: implement network connectivity test Joshua Lock
2011-06-19 15:03 ` Jeremy Puhlman
2011-06-20 16:20 ` Joshua Lock
2011-06-18 3:09 ` Joshua Lock [this message]
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=1308366548.2245.14.camel@scimitar \
--to=josh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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.