[OE-core] [RFC 0/2] Sanity check network connectivity
Joshua Lock
josh at linux.intel.com
Wed Jun 29 21:55:01 UTC 2011
v3 of this change set based on extra feedback from Khem Raj.
Changes since v2:
* Remove references to Yocto, don't offer default uri's to check
* Make the error message configurable through a variable, CONNECTIVITY_CHECK_MSG,
whilst providing a reasonable default.
"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 following changes since commit ff014d9634638457622f6019b163e75bafcefada:
task-base: add 3G into DISTRO_FEATURE (2011-06-29 14:46:46 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib josh/connection-test
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=josh/connection-test
Joshua Lock (2):
sanity.bbclass: pass the data object to the less frequent test
harnesses
sanity: implement network connectivity test
meta/classes/sanity.bbclass | 53 ++++++++++++++++++++++++++++++++++++------
1 files changed, 45 insertions(+), 8 deletions(-)
--
1.7.5.4
More information about the Openembedded-core
mailing list