From: Jeremy Puhlman <jpuhlman@mvista.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH 2/2] sanity: implement network connectivity test
Date: Sun, 19 Jun 2011 08:03:53 -0700 [thread overview]
Message-ID: <4DFE0FD9.4010400@mvista.com> (raw)
In-Reply-To: <f0a7d48483260e9251d74216d7569de1a029d035.1308365562.git.josh@linux.intel.com>
> + test_uris= ["http://yoctoproject.org/about",
> + "https://eula-downloads.yoctoproject.org/crownbay/crownbay-bernard-5.0.0",
> + "git://git.yoctoproject.org/yocto-firewall-test;protocol=git;rev=HEAD"]
> + retval = ""
These should probably be set as setable from the meta data. It is a
reasonable default, but hard coding it with out a way to change it is
probably not what we want.
> +
> + # Only check connectivity if network and this check enabled
> + # Because it's a fairy heavy test allow disabling of just this sanity test
> + # by setting DISABLE_NETWORK_SANITY
> + data = bb.data.createCopy(d)
> + network_disabled = not bb.data.getVar('BB_NO_NETWORK', data, True)
> + check_disabled = bb.data.getVar('DISABLE_NETWORK_SANITY', data, True)
> + if check_disabled or network_disabled:
Completely minor gnit. The copy here isn't needed until you start
setting the DL_DIR. Why not wait til after the check to see if we need
to do it.
Otherwise seem like a solid idea.
--
Jeremy Puhlman
Montavista Sofware, LLC.
next prev parent reply other threads:[~2011-06-19 15:07 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 [this message]
2011-06-20 16:20 ` Joshua Lock
2011-06-18 3:09 ` [RFC PATCH 0/2] Sanity testing network connectivity Joshua Lock
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=4DFE0FD9.4010400@mvista.com \
--to=jpuhlman@mvista.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.