Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: jackie.huang@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] staging.bbclass: make already-stripped can be skipped
Date: Wed, 16 Dec 2015 12:04:50 +0100	[thread overview]
Message-ID: <20151216110450.GA2767@jama> (raw)
In-Reply-To: <1450259641-19389-1-git-send-email-jackie.huang@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 1891 bytes --]

On Wed, Dec 16, 2015 at 05:54:01PM +0800, jackie.huang@windriver.com wrote:
> From: Jackie Huang <jackie.huang@windriver.com>
> 
> Add a check like what we does in package.bbclass
> so that the already-stripped QA test can be skipped.

Cannot we use package_qa_handle_error function here? So that these
issues end in qa.log and user/distro can easily define how important the
warning is for them?

> Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
> ---
>  meta/classes/staging.bbclass | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/classes/staging.bbclass b/meta/classes/staging.bbclass
> index 967eddd..243bcdf 100644
> --- a/meta/classes/staging.bbclass
> +++ b/meta/classes/staging.bbclass
> @@ -127,7 +127,10 @@ python sysroot_strip () {
>                      elf_file = isELF(file)
>                      if elf_file & 1:
>                          if elf_file & 2:
> -                            bb.warn("File '%s' from %s was already stripped, this will prevent future debugging!" % (file[len(dvar):], pn))
> +                            if 'already-stripped' in (d.getVar('INSANE_SKIP_' + pn, True) or "").split():
> +                                bb.note("Skipping file %s from %s for already-stripped QA test" % (file[len(dvar):], pn))
> +                            else:
> +                                bb.warn("File '%s' from %s was already stripped, this will prevent future debugging!" % (file[len(dvar):], pn))
>                              continue
>  
>                          if s.st_ino in inodes:
> -- 
> 2.3.5
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2015-12-16 11:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-16  9:54 [PATCH] staging.bbclass: make already-stripped can be skipped jackie.huang
2015-12-16 11:04 ` Martin Jansa [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=20151216110450.GA2767@jama \
    --to=martin.jansa@gmail.com \
    --cc=jackie.huang@windriver.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