From: Scott Mayhew <smayhew@redhat.com>
To: kdevops@lists.linux.dev
Subject: [PATCH 6/9] pynfs: add makefile target to show test results
Date: Mon, 3 Mar 2025 08:09:45 -0500 [thread overview]
Message-ID: <20250303130948.630029-7-smayhew@redhat.com> (raw)
In-Reply-To: <20250303130948.630029-1-smayhew@redhat.com>
Add 'pynfs-show-results' makefile target to show test results.
Under the hood, it more or less just does 'find ... | xargs cat'.
It shows the json results files for the most recent kernel run. You can
show the results for a differnt kernel by overriding the LAST_KERNEL
variable, e.g.
$ LAST_KERNEL=6.13.4-300.fc41.x86_64 make pynfs-show-results
Signed-off-by: Scott Mayhew <smayhew@redhat.com>
---
workflows/pynfs/Makefile | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/workflows/pynfs/Makefile b/workflows/pynfs/Makefile
index 75a4b6a..253a222 100644
--- a/workflows/pynfs/Makefile
+++ b/workflows/pynfs/Makefile
@@ -24,6 +24,10 @@ PYNFS_KERNEL_CI_LOOP := scripts/workflows/pynfs/run_kernel_ci.sh
PYNFS_KERNEL_CI_LOOP_KOTD := scripts/workflows/pynfs/run_kernel_ci_kotd.sh
endif # CONFIG_KERNEL_CI
+ifndef LAST_KERNEL
+LAST_KERNEL := $(shell cat workflows/pynfs/results/last-kernel.txt 2>/dev/null)
+endif
+
# Makefile for pynfs targets
pynfs:
$(Q)ansible-playbook $(ANSIBLE_VERBOSE) -l baseline,dev \
@@ -63,6 +67,14 @@ pynfs-dev-reset:
$(Q)ansible-playbook $(ANSIBLE_VERBOSE) \
-f 30 -i hosts -l dev playbooks/pynfs.yml --tags vars,reset --extra-vars=@./extra_vars.yaml
+pynfs-show-results:
+ifdef LAST_KERNEL
+ @find workflows/pynfs/results/$(LAST_KERNEL) -type f \
+ | xargs -I {} bash -c 'echo "{}:"; cat {}; echo -e "\n";'
+else
+ @echo "No results."
+endif
+
pynfs-help-menu:
@echo "pynfs options:"
@echo "pynfs - Git clone pynfs, build and install it"
--
2.48.1
next prev parent reply other threads:[~2025-03-03 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 13:09 [PATCH 0/9] tweak results organization and reporting Scott Mayhew
2025-03-03 13:09 ` [PATCH 1/9] pynfs: add last-run directory and last-kernel.txt to the results Scott Mayhew
2025-03-03 13:09 ` [PATCH 2/9] nfstest: " Scott Mayhew
2025-03-03 13:09 ` [PATCH 3/9] gitr: " Scott Mayhew
2025-03-03 13:09 ` [PATCH 4/9] ltp: " Scott Mayhew
2025-03-03 13:09 ` [PATCH 5/9] fstests: add makefile target to show test results Scott Mayhew
2025-03-06 16:48 ` Luis Chamberlain
2025-03-03 13:09 ` Scott Mayhew [this message]
2025-03-03 13:09 ` [PATCH 7/9] nfstest: " Scott Mayhew
2025-03-03 13:09 ` [PATCH 8/9] gitr: " Scott Mayhew
2025-03-03 13:09 ` [PATCH 9/9] ltp: " Scott Mayhew
2025-03-12 20:09 ` [PATCH 0/9] tweak results organization and reporting Chuck Lever
2025-03-12 22:58 ` Luis Chamberlain
-- strict thread matches above, loose matches on Subject: below --
2025-03-05 0:57 Scott Mayhew
2025-03-05 0:57 ` [PATCH 6/9] pynfs: add makefile target to show test results Scott Mayhew
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=20250303130948.630029-7-smayhew@redhat.com \
--to=smayhew@redhat.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