From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
Viacheslav Dubeyko <slava@dubeyko.com>,
kdevops@lists.linux.dev
Cc: Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 2/4] steady-state: fix identation on Makefile
Date: Thu, 17 Jul 2025 21:05:54 -0700 [thread overview]
Message-ID: <20250718040557.2774976-3-mcgrof@kernel.org> (raw)
In-Reply-To: <20250718040557.2774976-1-mcgrof@kernel.org>
ChatGPT Codex generated this code, it gets a B rating as I only found
one bug and this was it. I told it to borrow the stead-state code from
my plot-sysbench code [0] and also take my fio-tests language and
Kconfig logic from fio-tests [1].
And so I'll be folding in fio-tests to kdevops soon using kdevops as
this is proving to be quite simple with ChatGPT codex. I can say then
with more confidence that the architecture behind kdevops is making
adding more workflows with things like ChatGPT codex super simple. We
should be able to scale faster by now and recent developments / tools.
Link: https://github.com/mcgrof/plot-sysbench # [0]
Link: https://github.com/mcgrof/fio-tests # [1]
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
workflows/steady_state/Makefile | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/workflows/steady_state/Makefile b/workflows/steady_state/Makefile
index 56897111..6d395021 100644
--- a/workflows/steady_state/Makefile
+++ b/workflows/steady_state/Makefile
@@ -3,12 +3,12 @@ PHONY += steady-state steady-state-help-menu
SSD_STEADY_STATE_DYNAMIC_RUNTIME_VARS := "kdevops_run_ssd_steady_state": True
steady-state:
-$(Q)ansible-playbook $(ANSIBLE_VERBOSE) \
--i $(KDEVOPS_HOSTFILE) playbooks/steady_state.yml \
---extra-vars '{ $(SSD_STEADY_STATE_DYNAMIC_RUNTIME_VARS) }' $(LIMIT_HOSTS)
+ $(Q)ansible-playbook $(ANSIBLE_VERBOSE) \
+ -i $(KDEVOPS_HOSTFILE) playbooks/steady_state.yml \
+ --extra-vars '{ $(SSD_STEADY_STATE_DYNAMIC_RUNTIME_VARS) }' $(LIMIT_HOSTS)
steady-state-help-menu:
-@echo "steady-state - Prefill and run fio steady state"
-@echo ""
+ @echo "steady-state - Prefill and run fio steady state"
+ @echo ""
HELP_TARGETS += steady-state-help-menu
--
2.47.2
next prev parent reply other threads:[~2025-07-18 4:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 4:05 [PATCH 0/4] steady-state: few fixes for steady state support Luis Chamberlain
2025-07-18 4:05 ` [PATCH 1/4] steady-state: use extra sparse drives when on libvirt Luis Chamberlain
2025-07-18 4:05 ` Luis Chamberlain [this message]
2025-07-18 4:05 ` [PATCH 3/4] steady-state: remove extra menu Luis Chamberlain
2025-07-18 4:05 ` [PATCH 4/4] steady-state: quite a bit of fixes 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=20250718040557.2774976-3-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=cel@kernel.org \
--cc=da.gomez@kruces.com \
--cc=kdevops@lists.linux.dev \
--cc=slava@dubeyko.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