From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: mark.hatle@kernel.crashing.org, openembedded-core@lists.openembedded.org
Cc: mark.hatle@amd.com
Subject: Re: [OE-core] [PATCH v2 4/4] selftest-hardlink: Add additional test cases
Date: Fri, 19 Jul 2024 07:49:20 +0100 [thread overview]
Message-ID: <a0074123bff1eafead40e16f30c19d48d273b58b.camel@linuxfoundation.org> (raw)
In-Reply-To: <1721345282-10901-5-git-send-email-mark.hatle@kernel.crashing.org>
On Thu, 2024-07-18 at 18:28 -0500, Mark Hatle via lists.openembedded.org wrote:
> From: Mark Hatle <mark.hatle@amd.com>
>
> Additional test cases for debug symlink generation both binaries
> and static libraries.
>
> This also has the side effect of testing for race conditions in the
> hardlink debug generation and stripping.
>
> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
> Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
> ---
> .../selftest-hardlink/selftest-hardlink.bb | 13 ++++++++++++
> meta/lib/oeqa/selftest/cases/package.py | 24 ++++++++++++++++++++++
> 2 files changed, 37 insertions(+)
This caused selftest failures, e.g.:
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/6984/steps/14/logs/stdio
Cheers,
Richard
prev parent reply other threads:[~2024-07-19 6:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 23:27 [PATCH v2 0/4] Fix static-library related issues Mark Hatle
2024-07-18 23:27 ` [PATCH v2 1/4] package.py: Fix static debuginfo split Mark Hatle
2024-07-19 14:32 ` [OE-core] " Richard Purdie
2024-07-18 23:28 ` [PATCH v2 2/4] package.py: Fix inode link target Mark Hatle
2024-07-18 23:28 ` [PATCH v2 3/4] package.py: Fix static library processing Mark Hatle
2024-07-18 23:28 ` [PATCH v2 4/4] selftest-hardlink: Add additional test cases Mark Hatle
2024-07-19 6:49 ` Richard Purdie [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=a0074123bff1eafead40e16f30c19d48d273b58b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mark.hatle@amd.com \
--cc=mark.hatle@kernel.crashing.org \
--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