From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bastien Curutchet <bastien.curutchet@bootlin.com>
Cc: buildroot@buildroot.org, Fiona Klute <fiona.klute@gmx.de>
Subject: Re: [Buildroot] [PATCH 2/2] support/testing: add rasdaemon tests
Date: Wed, 26 Nov 2025 12:00:55 +0100 [thread overview]
Message-ID: <20251126120055.6dd94e90@windsurf> (raw)
In-Reply-To: <20251126-rasdaemon-v1-2-38c590f3e591@bootlin.com>
Hello,
On Wed, 26 Nov 2025 11:20:10 +0100
Bastien Curutchet <bastien.curutchet@bootlin.com> wrote:
> +class TestRasdaemon(infra.basetest.BRTest):
> + config = infra.basetest.BASIC_TOOLCHAIN_CONFIG + \
> + """
> + BR2_PACKAGE_RASDAEMON=y
> + BR2_PACKAGE_RASDAEMON_AER=y
> + BR2_PACKAGE_LIBTRACEEVENT=y
> + BR2_PACKAGE_SQLITE=y
> + BR2_PACKAGE_PCIUTILS=y
> + BR2_TARGET_ROOTFS_CPIO=y
> + # BR2_TARGET_ROOTFS_TAR is not set
> + """
> +
> + def test_run(self):
> + cpio_file = os.path.join(self.builddir, "images", "rootfs.cpio")
> + self.emulator.boot(arch="armv7",
> + kernel="builtin",
> + options=["-initrd", cpio_file])
> + self.emulator.login()
> +
> + self.assertRunOk("/usr/sbin/rasdaemon --version")
Since it installs an init script, what about checking that the daemon
is actually running?
Bonus point if you're actually able to inject an error, and verify that
rasdaemon reacts to it by running some arbitrary action :-)
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
next prev parent reply other threads:[~2025-11-26 11:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 10:20 [Buildroot] [PATCH 0/2] package: add rasdaemon support Bastien Curutchet via buildroot
2025-11-26 10:20 ` [Buildroot] [PATCH 1/2] package/rasdaemon: Add rasdaemon package Bastien Curutchet via buildroot
2025-11-26 10:59 ` Thomas Petazzoni via buildroot
2025-11-26 14:57 ` Bastien Curutchet via buildroot
2025-11-26 14:32 ` Fiona Klute via buildroot
2025-11-26 14:46 ` Bastien Curutchet via buildroot
2025-11-26 16:35 ` Fiona Klute via buildroot
2025-11-27 7:45 ` Bastien Curutchet via buildroot
2025-11-26 10:20 ` [Buildroot] [PATCH 2/2] support/testing: add rasdaemon tests Bastien Curutchet via buildroot
2025-11-26 11:00 ` Thomas Petazzoni via buildroot [this message]
2025-11-26 14:58 ` Bastien Curutchet via buildroot
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=20251126120055.6dd94e90@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