From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bastien Curutchet via buildroot <buildroot@buildroot.org>
Cc: Bastien Curutchet <bastien.curutchet@bootlin.com>,
Fiona Klute <fiona.klute@gmx.de>
Subject: Re: [Buildroot] [PATCH v4 2/2] support/testing: add rasdaemon tests
Date: Wed, 31 Dec 2025 10:48:00 +0100 [thread overview]
Message-ID: <20251231104800.115fbed6@windsurf> (raw)
In-Reply-To: <20251219-rasdaemon-v4-2-2cdc992de787@bootlin.com>
Hello Bastien,
On Fri, 19 Dec 2025 17:30:16 +0100
Bastien Curutchet via buildroot <buildroot@buildroot.org> wrote:
> Rasdaemon was added in previous patch.
>
> Add a test_rasdaemon that allows to test it.
> Test is done on x86. It first checks the daemon's version, then mounts
> debugfs and finally ensures that the init script allows to
> start/restart/stop the daemon.
>
> Signed-off-by: Bastien Curutchet <bastien.curutchet@bootlin.com>
I've applied, after doing some changes, see below.
> +class TestRasdaemon(infra.basetest.BRTest):
> + config = f"""
> + BR2_x86_64=y
> + BR2_x86_corei7=y
> + BR2_INIT_SYSV=y
This was not needed, the default init system (Busybox) is fine.
> + BR2_LINUX_KERNEL=y
> + BR2_TOOLCHAIN_EXTERNAL=y
> + BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> + BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.12.59"
> + BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
> + BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/qemu/x86/linux.config"
> + BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="{infra.filepath("tests/package/test_rasdaemon/linux-debugfs.fragment")}"
This kernel wouldn't build as host-libelf and host-openssl were
missing, so I've added:
+ BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
+ BR2_LINUX_KERNEL_NEEDS_HOST_LIBELF=y
Applied with those changes; Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-12-31 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 16:30 [Buildroot] [PATCH v4 0/2] package: add rasdaemon support Bastien Curutchet via buildroot
2025-12-19 16:30 ` [Buildroot] [PATCH v4 1/2] package/rasdaemon: Add rasdaemon package Bastien Curutchet via buildroot
2025-12-31 9:46 ` Thomas Petazzoni via buildroot
2025-12-19 16:30 ` [Buildroot] [PATCH v4 2/2] support/testing: add rasdaemon tests Bastien Curutchet via buildroot
2025-12-31 9:48 ` Thomas Petazzoni via buildroot [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=20251231104800.115fbed6@windsurf \
--to=buildroot@buildroot.org \
--cc=bastien.curutchet@bootlin.com \
--cc=fiona.klute@gmx.de \
--cc=thomas.petazzoni@bootlin.com \
/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