Openembedded Core Discussions
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: mingli.yu@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] elfutils: fix ptest failures
Date: Wed, 29 May 2019 19:40:15 +0100	[thread overview]
Message-ID: <db641393dee9ad005cc693a8dc623afa6bdcd19f.camel@linuxfoundation.org> (raw)
In-Reply-To: <1559120138-3450-1-git-send-email-mingli.yu@windriver.com>

On Wed, 2019-05-29 at 16:55 +0800, mingli.yu@windriver.com wrote:
> From: Mingli Yu <Mingli.Yu@windriver.com>
> 
> * Add missing -ptest package dependency (needs
>   ${PN}-dev)
> 
> * Add missing files which needed by ptest test
>   to fix the ptest failures such as:
>   | sh: ../src/elflint: No such file or directory
>   | FAIL: asm-tst4
> 
> * Rework 0001-skip-the-test-when-gcc-not-deployed.patch
>   to skip the tests which depend on gcc
> 
> * Define INHIBIT_PACKAGE_STRIP_FILES for elfutils to
>   avoid stripping some generated binaries otherwise
>   some of the tests such as test-nlist, run-strip-reloc.sh,
>   run-strip-strmerge.sh and so on will fail
> 
> Before:
> --------------------------------------------
> Recipe   | Passed    | Failed   | Skipped
> --------------------------------------------
> elfutils | 176       | 23       | 4
> --------------------------------------------
> 
> After:
> --------------------------------------------
> Recipe   | Passed    | Failed   | Skipped
> --------------------------------------------
> elfutils | 199       | 0       | 4
> --------------------------------------------
> 
> Signed-off-by: Mingli Yu <Mingli.Yu@windriver.com>

I tested this without the libdir strip lines and it fails on musl:

https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/645

Cheers,

Richard



  parent reply	other threads:[~2019-05-29 18:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22  9:11 [PATCH] elfutils: fix ptest failures mingli.yu
2019-05-25 20:16 ` richard.purdie
2019-05-28  9:31   ` Yu, Mingli
2019-05-28  9:40   ` [PATCH v2] " mingli.yu
2019-05-28 10:01     ` richard.purdie
2019-05-29  2:59       ` Yu, Mingli
2019-05-29  8:55       ` [PATCH v3] " mingli.yu
2019-05-29 10:13         ` richard.purdie
2019-05-30  6:03           ` Yu, Mingli
2019-05-30  6:11           ` [PATCH v4] " mingli.yu
2019-05-30 20:49             ` richard.purdie
2019-05-30 22:16               ` Richard Purdie
2019-05-31  6:40               ` Yu, Mingli
2019-05-31  8:48                 ` richard.purdie
2019-05-31  9:44                   ` [PATCH v5] " mingli.yu
2019-05-29 18:40         ` richard.purdie [this message]
2019-05-30  6:04           ` [PATCH v3] " Yu, Mingli

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=db641393dee9ad005cc693a8dc623afa6bdcd19f.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mingli.yu@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