Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] bitbake/ui/knotty: Ensure 'No Provider' errors set an exit code
Date: Tue, 09 Aug 2011 09:25:31 -0700	[thread overview]
Message-ID: <1312907137.2265.2.camel@scimitar> (raw)
In-Reply-To: <1312897403.14274.295.camel@rex>

On Tue, 2011-08-09 at 14:43 +0100, Richard Purdie wrote:
> If a No Provider error is shown we need to set the exit code to
> show an error occured too.
> 
> [YOCTO #1322]
> 
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

Signed-off-by: Joshua Lock <josh@linux.intel.com>

> ---
> diff --git a/bitbake/lib/bb/ui/knotty.py b/bitbake/lib/bb/ui/knotty.py
> index b7abdf8..63b8dc6 100644
> --- a/bitbake/lib/bb/ui/knotty.py
> +++ b/bitbake/lib/bb/ui/knotty.py
> @@ -199,6 +199,7 @@ def main(server, eventHandler):
>                  logger.info("consider defining a PREFERRED_PROVIDER entry to match %s", event._item)
>                  continue
>              if isinstance(event, bb.event.NoProvider):
> +                return_value = 1
>                  if event._runtime:
>                      r = "R"
>                  else:
> 
> 
> 
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel

-- 
Joshua Lock
        Yocto Project "Johannes factotum"
        Intel Open Source Technology Centre




      reply	other threads:[~2011-08-09 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09 13:43 [PATCH] bitbake/ui/knotty: Ensure 'No Provider' errors set an exit code Richard Purdie
2011-08-09 16:25 ` 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=1312907137.2265.2.camel@scimitar \
    --to=josh@linux.intel.com \
    --cc=bitbake-devel@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