Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] sanity.bbclass: trigger network tests explicitly
Date: Thu, 18 Oct 2012 13:16:10 -0700	[thread overview]
Message-ID: <5080638A.4040206@linux.intel.com> (raw)
In-Reply-To: <1349955886-6399-1-git-send-email-bogdan.a.marinescu@intel.com>

On 10/11/2012 04:44 AM, Bogdan Marinescu wrote:
> The network tests in sanity.bbclass can now be trigerred explicitly
> by firing the NetworkTest event. This is part of the fix for bug #3026.
>
> [YOCTO #3026]
>
> Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
> ---
>   meta/classes/sanity.bbclass |    3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
> index f2e9a74..3806bc5 100644
> --- a/meta/classes/sanity.bbclass
> +++ b/meta/classes/sanity.bbclass
> @@ -639,6 +639,9 @@ python check_sanity_eventhandler() {
>           sanity_data.setVar("SANITY_USE_EVENTS", "1")
>           check_sanity(sanity_data)
>           bb.event.fire(bb.event.SanityCheckPassed(), e.data)
> +    elif bb.event.getName(e) == "NetworkTest":
> +        sanity_data = copy_data(e)
> +        bb.event.fire(bb.event.NetworkTestFailed() if check_connectivity(sanity_data) else bb.event.NetworkTestPassed(), e.data)
>
>       return
>   }
>
Merged into OE-Core

Thanks
	Sau!




      reply	other threads:[~2012-10-18 20:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-11 11:44 [PATCH 1/2] sanity.bbclass: trigger network tests explicitly Bogdan Marinescu
2012-10-18 20:16 ` Saul Wold [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=5080638A.4040206@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=bogdan.a.marinescu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox