From: Scott Mayhew <smayhew@redhat.com>
To: kdevops@lists.linux.dev
Subject: [PATCH 7/9] nfstest: add makefile target to show test results
Date: Tue, 4 Mar 2025 19:57:52 -0500 [thread overview]
Message-ID: <20250305005755.697599-9-smayhew@redhat.com> (raw)
In-Reply-To: <20250305005755.697599-1-smayhew@redhat.com>
Under the hood, it more or less just does 'find ... | xargs cat'.
It shows the text results files for the most recent kernel run. You can
show the results for a different kernel by overriding the LAST_KERNEL
variable, e.g.
$ LAST_KERNEL=6.13.4-300.fc41.x86_64 make nfstest-show-results
Note that since the nfstest log files have a date and timestamp in the
filename, it's possible to accumulate logs from multiple test runs. If
you're showing the results from the most recent kernel, then we'll only
show the logs from the most recent run (i.e. logs that are newer than
the timestamp of the last-run directory). But if you're showing the
results from an older kernel, then we'll show all the logs in that
directory (but you can change that by overriding the PATTERN variable).
Signed-off-by: Scott Mayhew <smayhew@redhat.com>
---
workflows/nfstest/Makefile | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/workflows/nfstest/Makefile b/workflows/nfstest/Makefile
index 638ec1f..2e645ce 100644
--- a/workflows/nfstest/Makefile
+++ b/workflows/nfstest/Makefile
@@ -53,6 +53,10 @@ NFSTEST_KERNEL_CI_LOOP := scripts/workflows/nfstest/run_kernel_ci.sh
NFSTEST_KERNEL_CI_LOOP_KOTD := scripts/workflows/nfstest/run_kernel_ci_kotd.sh
endif # CONFIG_KERNEL_CI
+ifndef LAST_KERNEL
+LAST_KERNEL := $(shell cat workflows/nfstest/results/last-kernel.txt 2>/dev/null)
+endif
+
nfstest:
$(Q)ansible-playbook $(ANSIBLE_VERBOSE) -l baseline,dev \
-f 30 -i hosts playbooks/nfstest.yml \
@@ -88,6 +92,19 @@ nfstest-dev-reset:
--tags vars,reset \
--extra-vars=@./extra_vars.yaml
+nfstest-show-results:
+ifdef LAST_KERNEL
+ifeq ($(LAST_KERNEL), $(shell cat workflows/nfstest/results/last-kernel.txt 2>/dev/null))
+ @find workflows/nfstest/results/$(LAST_KERNEL) -type f $(PATTERN) -newer workflows/nfstest/results/last-run \
+ | xargs -I {} bash -c 'echo "{}:"; cat {}; echo;'
+else
+ @find workflows/nfstest/results/$(LAST_KERNEL) -type f $(PATTERN) \
+ | xargs -I {} bash -c 'echo "{}:"; cat {}; echo;'
+endif
+else
+ @echo "No results."
+endif
+
nfstest-help-menu:
@echo "nfstest options:"
@echo "nfstest - Git clone nfstest and install it"
--
2.48.1
next prev parent reply other threads:[~2025-03-05 0:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 0:57 [PATCH 0/9] tweak results organization and reporting Scott Mayhew
2025-03-05 0:57 ` [PATCH] Don't include the codereadyrepo role if we're using a custom yum repofile Scott Mayhew
2025-03-05 0:57 ` [PATCH 1/9] pynfs: add last-run directory and last-kernel.txt to the results Scott Mayhew
2025-03-05 0:57 ` [PATCH 2/9] nfstest: " Scott Mayhew
2025-03-05 0:57 ` [PATCH 3/9] gitr: " Scott Mayhew
2025-03-05 0:57 ` [PATCH 4/9] ltp: " Scott Mayhew
2025-03-05 0:57 ` [PATCH 5/9] fstests: add makefile target to show test results Scott Mayhew
2025-03-05 0:57 ` [PATCH 6/9] pynfs: " Scott Mayhew
2025-03-05 0:57 ` Scott Mayhew [this message]
2025-03-05 0:57 ` [PATCH 8/9] gitr: " Scott Mayhew
2025-03-05 0:57 ` [PATCH 9/9] ltp: " Scott Mayhew
2025-03-05 0:57 ` [PATCH] Don't include the codereadyrepo role if we're using a custom yum repofile Scott Mayhew
2025-03-05 1:11 ` [PATCH 0/9] tweak results organization and reporting Scott Mayhew
-- strict thread matches above, loose matches on Subject: below --
2025-03-03 13:09 Scott Mayhew
2025-03-03 13:09 ` [PATCH 7/9] nfstest: 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=20250305005755.697599-9-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