From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ecordonnier@snap.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] oeqa/runtime: fix regression in minidebuginfo test
Date: Wed, 29 May 2024 15:54:42 +0100 [thread overview]
Message-ID: <80be0806edba87cb67f7f5711fb9c83516fb860d.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240529100853.1162640-1-ecordonnier@snap.com>
On Wed, 2024-05-29 at 12:08 +0200, Etienne Cordonnier via lists.openembedded.org wrote:
> From: Etienne Cordonnier <ecordonnier@snap.com>
>
> The builtin command "sleep" was getting executed instead of the busybox binary.
> Hence "pidof sleep" was empty and the test was failing.
>
> Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
> ---
> meta/lib/oeqa/runtime/cases/systemd.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/lib/oeqa/runtime/cases/systemd.py b/meta/lib/oeqa/runtime/cases/systemd.py
> index 5481e1d840..a2229848e7 100644
> --- a/meta/lib/oeqa/runtime/cases/systemd.py
> +++ b/meta/lib/oeqa/runtime/cases/systemd.py
> @@ -145,7 +145,7 @@ class SystemdServiceTests(SystemdTest):
> Verify that call-stacks generated by systemd-coredump contain symbolicated call-stacks,
> extracted from the minidebuginfo metadata (.gnu_debugdata elf section).
> """
> - t_thread = threading.Thread(target=self.target.run, args=("ulimit -c unlimited && sleep 1000",))
> + t_thread = threading.Thread(target=self.target.run, args=("ulimit -c unlimited && /usr/bin/sleep 1000",))
> t_thread.start()
> time.sleep(1)
I get a bit nervous about hardcoding paths like "/usr/bin",
particularly in the context of some distros liking to move things
around. We may want to put a shutil.which("sleep") call in instead (and
an import shutil if needed)?
Cheers,
Richard
next prev parent reply other threads:[~2024-05-29 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 10:08 [PATCH] oeqa/runtime: fix regression in minidebuginfo test ecordonnier
2024-05-29 14:54 ` Richard Purdie [this message]
2024-05-30 15:23 ` [OE-core] " Etienne Cordonnier
[not found] ` <17D44D900E0F42D1.15404@lists.openembedded.org>
2024-06-03 11:35 ` Etienne Cordonnier
2024-06-03 11:42 ` Alexander Kanavin
2024-06-03 14:13 ` Richard Purdie
[not found] ` <17D5840BB429ED6B.21428@lists.openembedded.org>
2024-06-03 14:28 ` Richard Purdie
2024-06-04 11:45 ` Etienne Cordonnier
2024-06-04 11:56 ` Richard Purdie
2024-06-04 11:58 ` Etienne Cordonnier
2024-06-04 12:32 ` Richard Purdie
2024-06-05 10:11 ` Etienne Cordonnier
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=80be0806edba87cb67f7f5711fb9c83516fb860d.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=ecordonnier@snap.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