From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
kdevops@lists.linux.dev
Cc: Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 7/8] fstests: add make target for running tests on all hosts
Date: Mon, 11 Aug 2025 15:43:06 -0700 [thread overview]
Message-ID: <20250811224307.2218478-8-mcgrof@kernel.org> (raw)
In-Reply-To: <20250811224307.2218478-1-mcgrof@kernel.org>
Add a new 'fstests-tests' make target that runs tests on both baseline
and dev hosts simultaneously. This target is useful for A/B testing
scenarios where you want to run the same tests on multiple host
configurations in parallel.
The target uses the same FSTESTS_DYNAMIC_RUNTIME_VARS as the existing
baseline and dev targets but limits execution to both baseline and dev
host groups together.
Generated-by: Claude AI
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
workflows/fstests/Makefile | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/workflows/fstests/Makefile b/workflows/fstests/Makefile
index 77f8055c..64a9b61c 100644
--- a/workflows/fstests/Makefile
+++ b/workflows/fstests/Makefile
@@ -198,6 +198,15 @@ fstests-dev: $(KDEVOPS_EXTRA_VARS)
'{ $(FSTESTS_DYNAMIC_RUNTIME_VARS) }' \
--extra-vars=@./extra_vars.yaml $(LIMIT_HOSTS)
+fstests-tests: $(KDEVOPS_EXTRA_VARS)
+ $(Q)ansible-playbook $(ANSIBLE_VERBOSE) \
+ --limit 'baseline:dev' \
+ playbooks/fstests.yml \
+ --tags vars,run_tests,copy_results \
+ --extra-vars \
+ '{ $(FSTESTS_DYNAMIC_RUNTIME_VARS) }' \
+ --extra-vars=@./extra_vars.yaml $(LIMIT_HOSTS)
+
fstests-baseline-results-tfb-ls: $(KDEVOPS_EXTRA_VARS)
$(Q)ansible-playbook $(ANSIBLE_VERBOSE) \
--limit 'baseline' \
@@ -249,6 +258,7 @@ fstests-help-menu:
@echo "fstests-kdevops-setup - Install kdevops specific files, the fstests and running test targets also runs this"
@echo "fstests-baseline - Run fstests on baseline hosts and collect results"
@echo "fstests-dev - Run fstests on dev hosts and collect results"
+ @echo "fstests-tests - Run fstests on both baseline and dev hosts simultaneously"
@echo ""
@echo "fstests-config - Generates the filesystem configuration file only onto target systems"
@echo "fstests-config-debug - Generates the filesystem configuration file locally, useful for debugging"
--
2.47.2
next prev parent reply other threads:[~2025-08-11 22:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 22:42 [PATCH 0/8] linux-ab enhancements + monitor support Luis Chamberlain
2025-08-11 22:43 ` [PATCH 1/8] bootlinux: use different kernel for A/B testing by default Luis Chamberlain
2025-08-11 22:43 ` [PATCH 2/8] bootlinux: add support for custom refs on dev kernels on the CLI Luis Chamberlain
2025-08-11 22:43 ` [PATCH 3/8] bootlinux: add git ref verification before cloning Luis Chamberlain
2025-08-11 22:43 ` [PATCH 4/8] bootlinux: add git dirty check " Luis Chamberlain
2025-08-11 22:43 ` [PATCH 5/8] bootlinux: add intelligent git repository detection and management Luis Chamberlain
2025-08-11 22:43 ` [PATCH 6/8] bootlinux: enhance A/B testing and repository management Luis Chamberlain
2025-08-11 22:43 ` Luis Chamberlain [this message]
2025-08-11 22:43 ` [PATCH 8/8] monitoring: integrate monitoring collection into fstests workflow Luis Chamberlain
2025-08-11 22:46 ` Luis Chamberlain
2025-08-12 0:49 ` Luis Chamberlain
2025-08-14 0:59 ` Luis Chamberlain
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=20250811224307.2218478-8-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=cel@kernel.org \
--cc=da.gomez@kruces.com \
--cc=kdevops@lists.linux.dev \
/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