From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Jules Maselbas <jmaselbas@zdiv.net>,
jre@pengutronix.de, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 5/6] ci: pytest: run test suite on sandbox allyesconfig
Date: Wed, 26 Mar 2025 08:59:18 +0100 [thread overview]
Message-ID: <20250326075919.3448789-6-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20250326075919.3448789-1-a.fatoum@pengutronix.de>
Building allyesconfig in CI allows us to catch early compile-time
breakage when changes are done treewide. Running pytest over it
will ensure that compile-tested drivers don't break normal startup
when unused.
Additionally, allyesconfig also enables ASAN/UBSAN, which is a nice side
effect. A future change would be adding KASAN for other architectures as
well.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
.github/workflows/test-labgrid-pytest.yml | 4 ++++
test/sandbox/allyesconfig.yaml | 17 +++++++++++++++++
2 files changed, 21 insertions(+)
create mode 100644 test/sandbox/allyesconfig.yaml
diff --git a/.github/workflows/test-labgrid-pytest.yml b/.github/workflows/test-labgrid-pytest.yml
index 2a9f7a53aced..c43649e85fec 100644
--- a/.github/workflows/test-labgrid-pytest.yml
+++ b/.github/workflows/test-labgrid-pytest.yml
@@ -55,6 +55,10 @@ jobs:
lgenv: 'test/sandbox/sandbox_defconfig.yaml'
defconfig: sandbox_defconfig
+ - ARCH: sandbox
+ lgenv: 'test/sandbox/allyesconfig.yaml'
+ defconfig: sandbox_defconfig
+
steps:
- name: Checkout code
uses: actions/checkout@v4
diff --git a/test/sandbox/allyesconfig.yaml b/test/sandbox/allyesconfig.yaml
new file mode 100644
index 000000000000..76b995127651
--- /dev/null
+++ b/test/sandbox/allyesconfig.yaml
@@ -0,0 +1,17 @@
+targets:
+ main:
+ drivers:
+ ExternalConsoleDriver:
+ cmd: !template "$LG_BUILDDIR/barebox"
+ ExternalPowerDriver:
+ cmd_on: 'true'
+ cmd_off: 'true'
+ BareboxDriver:
+ prompt: "barebox@[^:]+:[^ ]+ "
+ BareboxTestStrategy: {}
+ runner:
+ kconfig_add:
+ - CONFIG_CONSOLE_DISABLE_INPUT=n
+ - CONFIG_MALLOC_LIBC=y # for ASAN integration
+imports:
+ - ../strategy.py
--
2.39.5
next prev parent reply other threads:[~2025-03-26 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 7:59 [PATCH 0/6] ci: run tests and static analysis on allyesconfig Ahmad Fatoum
2025-03-26 7:59 ` [PATCH 1/6] sandbox: use CROSS_PKG_CONFIG when compiling sandbox arch code Ahmad Fatoum
2025-03-26 7:59 ` [PATCH 2/6] sandbox: hide sdl/libftdi symbols if libraries not found Ahmad Fatoum
2025-03-26 7:59 ` [PATCH 3/6] MAKEALL: fix check_pipe_status usage Ahmad Fatoum
2025-03-26 7:59 ` [PATCH 4/6] MAKEALL: remove use of alias in script Ahmad Fatoum
2025-03-26 7:59 ` Ahmad Fatoum [this message]
2025-03-26 7:59 ` [PATCH 6/6] ci: run static analysis on allyesconfig Ahmad Fatoum
2025-03-27 9:24 ` [PATCH 0/6] ci: run tests and " Sascha Hauer
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=20250326075919.3448789-6-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jmaselbas@zdiv.net \
--cc=jre@pengutronix.de \
/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