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 16/23] reboot-limit: add A/B testing support targets
Date: Mon, 11 Aug 2025 15:24:43 -0700 [thread overview]
Message-ID: <20250811222452.2213071-17-mcgrof@kernel.org> (raw)
In-Reply-To: <20250811222452.2213071-1-mcgrof@kernel.org>
Add missing targets to support A/B testing workflow:
- reboot-limit-tests: runs tests on both baseline and dev groups
- reboot-limit-dev: runs tests on dev group only
Rename the confusing reboot-limit-dev-baseline target to just
reboot-limit-dev. The "dev-baseline" naming was nonsensical as it
mixed two opposing concepts - "dev" refers to development/testing
nodes while "baseline" refers to the control group. Following the
pattern of other workflows like fstests, the dev target should
simply be named reboot-limit-dev.
Also updated help menu to document all available targets including
the previously undocumented dev-loop and dev-kotd targets.
This enables proper A/B testing with linux-ab workflow where users
can test different kernels on baseline and dev groups simultaneously.
Generated-by: Claude AI
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
workflows/demos/reboot-limit/Makefile | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/workflows/demos/reboot-limit/Makefile b/workflows/demos/reboot-limit/Makefile
index abc5b3d0..438acbec 100644
--- a/workflows/demos/reboot-limit/Makefile
+++ b/workflows/demos/reboot-limit/Makefile
@@ -163,8 +163,11 @@ reboot-limit-baseline-reset:
--tags vars,reset \
--extra-vars=@./extra_vars.yaml
+# This runs tests on both baseline and dev groups - useful for A/B testing
+reboot-limit-tests: reboot-limit-baseline reboot-limit-dev
+
# Below are the corresponding dev targets
-reboot-limit-dev-baseline:
+reboot-limit-dev:
$(Q)ansible-playbook $(ANSIBLE_VERBOSE) \
--limit 'dev' \
playbooks/reboot-limit.yml \
@@ -202,8 +205,11 @@ reboot-limit-help-menu:
@echo "reboot-limit-baseline - Run the reboot-limit test on baseline hosts and collect results"
@echo "reboot-limit-baseline-reset - Reset the test boot counter for baseline"
@echo "reboot-limit-dev - Run the reboot-limit test on dev hosts and collect results"
+ @echo "reboot-limit-tests - Run the reboot-limit test on both baseline and dev hosts (A/B testing)"
@echo "reboot-limit-baseline-loop - Run the reboot-limit test in a loop until failure or steady state"
@echo "reboot-limit-baseline-kotd - Run the reboot-limit kotd (kernel-of-the-day) loop"
+ @echo "reboot-limit-dev-loop - Run the reboot-limit test in a loop on dev hosts"
+ @echo "reboot-limit-dev-kotd - Run the reboot-limit kotd loop on dev hosts"
@echo "reboot-limit-results - Analyze and summarize reboot-limit test results"
@echo "reboot-limit-graph - Generate graphs from reboot-limit test results"
@echo ""
--
2.47.2
next prev parent reply other threads:[~2025-08-11 22:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 22:24 [PATCH 00/23] remove old kernel-ci and enhance reboot-limit Luis Chamberlain
2025-08-11 22:24 ` [PATCH 01/23] fstests: remove CONFIG_KERNEL_CI support Luis Chamberlain
2025-08-11 22:24 ` [PATCH 02/23] fstests: remove kernel-ci script symlinks Luis Chamberlain
2025-08-11 22:24 ` [PATCH 03/23] blktests: remove CONFIG_KERNEL_CI support Luis Chamberlain
2025-08-11 22:24 ` [PATCH 04/23] gitr: " Luis Chamberlain
2025-08-11 22:24 ` [PATCH 05/23] ltp: " Luis Chamberlain
2025-08-11 22:24 ` [PATCH 06/23] nfstest: " Luis Chamberlain
2025-08-11 22:24 ` [PATCH 07/23] pynfs: " Luis Chamberlain
2025-08-11 22:24 ` [PATCH 08/23] reboot-limit: convert CONFIG_KERNEL_CI to internal loop feature Luis Chamberlain
2025-08-11 22:24 ` [PATCH 09/23] kconfig: remove CONFIG_KERNEL_CI infrastructure Luis Chamberlain
2025-08-11 22:24 ` [PATCH 10/23] scripts: remove kernel-ci loop infrastructure Luis Chamberlain
2025-08-11 22:24 ` [PATCH 11/23] reboot-limit: simplify what gets selected Luis Chamberlain
2025-08-11 22:24 ` [PATCH 12/23] reboot-limit: add graph visualization support for results Luis Chamberlain
2025-08-11 22:24 ` [PATCH 13/23] reboot-limit: save graphs in organized results/graphs directory Luis Chamberlain
2025-08-11 22:24 ` [PATCH 14/23] docs: add comprehensive reboot-limit workflow documentation Luis Chamberlain
2025-08-11 22:24 ` [PATCH 15/23] reboot-limit: add kexec-tools dependency installation Luis Chamberlain
2025-08-11 22:24 ` Luis Chamberlain [this message]
2025-08-11 22:24 ` [PATCH 17/23] reboot-limit: fix kexec and reboot connection handling Luis Chamberlain
2025-08-11 22:24 ` [PATCH 18/23] reboot-limit: add COUNT parameter to override reboot count Luis Chamberlain
2025-08-11 22:24 ` [PATCH 19/23] reboot-limit: fix wait_for tasks using wrong host reference Luis Chamberlain
2025-08-11 22:24 ` [PATCH 20/23] reboot-limit: use ansible reboot module for all reboot types Luis Chamberlain
2025-08-11 22:24 ` [PATCH 21/23] reboot-limit: fix COUNT parameter to properly override reboot count Luis Chamberlain
2025-08-11 22:24 ` [PATCH 22/23] reboot-limit: handle empty dev group gracefully Luis Chamberlain
2025-08-11 22:24 ` [PATCH 23/23] reboot-limit: add kexec comparison feature Luis Chamberlain
2025-08-12 15:06 ` [PATCH 00/23] remove old kernel-ci and enhance reboot-limit Chuck Lever
2025-08-13 1:28 ` 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=20250811222452.2213071-17-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.