From: Scott Mayhew <smayhew@redhat.com>
To: kdevops@lists.linux.dev
Subject: [PATCH 5/9] fstests: add makefile target to show test results
Date: Mon, 3 Mar 2025 08:09:44 -0500 [thread overview]
Message-ID: <20250303130948.630029-6-smayhew@redhat.com> (raw)
In-Reply-To: <20250303130948.630029-1-smayhew@redhat.com>
Add 'fstests-show-results' makefile target to show test results.
Under the hood, it more or less just does 'find ... | xargs cat'.
By default, the result.xml files will be shown 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 fstests-show-results
You can change the files being shown by overriding the PATTERN variable.
For example, to just see the summary:
$ PATTERN="\( -name xunit_results.txt \)" make fstests-show-results
or to see the summary and the bad results:
$ PATTERN="\( -name xunit_results.txt -o -name \"*.bad\" \)" make fstests-show-results
or you can do any combination thereof, e.g.
$ LAST_KERNEL=6.13.4-300.fc41.x86_64 PATTERN="\( -name xunit_results.txt \)" make fstests-show-results
Signed-off-by: Scott Mayhew <smayhew@redhat.com>
---
workflows/fstests/Makefile | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/workflows/fstests/Makefile b/workflows/fstests/Makefile
index 344a1f8..ef9c0fa 100644
--- a/workflows/fstests/Makefile
+++ b/workflows/fstests/Makefile
@@ -115,6 +115,14 @@ ifneq (,$(COUNT))
FSTESTS_DYNAMIC_RUNTIME_VARS += , "oscheck_extra_args": "-I $(COUNT)"
endif
+ifndef LAST_KERNEL
+LAST_KERNEL := $(shell cat workflows/fstests/results/last-kernel.txt 2>/dev/null)
+endif
+
+ifndef PATTERN
+PATTERN := -name result.xml
+endif
+
fstests: $(FSTESTS_BASELINE_EXTRA)
$(Q)ansible-playbook $(ANSIBLE_VERBOSE) -l localhost,baseline,dev \
-f 30 -i hosts playbooks/fstests.yml --skip-tags run_tests,copy_results $(LIMIT_HOSTS)
@@ -218,6 +226,14 @@ fstests-dev-results: $(KDEVOPS_EXTRA_VARS)
--extra-vars=@./extra_vars.yaml \
$(LIMIT_HOSTS)
+fstests-show-results:
+ifdef LAST_KERNEL
+ @find workflows/fstests/results/$(LAST_KERNEL) -type f $(PATTERN) \
+ | xargs -I {} bash -c 'echo "{}:"; cat {}; echo;'
+else
+ @echo "No results."
+endif
+
fstests-help-menu:
@echo "fstests options:"
@echo "fstests - Git clones fstests, builds 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 ` Scott Mayhew [this message]
2025-03-06 16:48 ` [PATCH 5/9] fstests: add makefile target to show test results Luis Chamberlain
2025-03-03 13:09 ` [PATCH 6/9] pynfs: " Scott Mayhew
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 5/9] fstests: 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-6-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