From: Eugenio Zuccarelli <eugenio.zuccarelli@gmail.com>
To: brendan.higgins@linux.dev, david@davidgow.net, corbet@lwn.net
Cc: raemoar63@gmail.com, skhan@linuxfoundation.org,
rdunlap@infradead.org, linux-kselftest@vger.kernel.org,
kunit-dev@googlegroups.com, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Documentation: kunit: document --summary and --failed options
Date: Tue, 20 Oct 2026 12:10:33 +0000 [thread overview]
Message-ID: <179250646543.2190262.8632957027583518623@gmail.com> (raw)
Commit 062a9dd9bad7 ("kunit: tool: Only print the summary") and commit
3c67a2c09b3c ("kunit: tool: print failed tests only") added the --summary
and --failed options to kunit.py, but the matching entries in the
run_wrapper documentation were never added.
Add descriptions for both options next to the other output options, so
the documentation lists the arguments the tool actually accepts.
Assisted-by: LLM
Signed-off-by: Eugenio Zuccarelli <eugenio.zuccarelli@gmail.com>
---
Documentation/dev-tools/kunit/run_wrapper.rst | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/dev-tools/kunit/run_wrapper.rst b/Documentation/dev-tools/kunit/run_wrapper.rst
index cecc110a..641ab50a 100644
--- a/Documentation/dev-tools/kunit/run_wrapper.rst
+++ b/Documentation/dev-tools/kunit/run_wrapper.rst
@@ -327,6 +327,14 @@ command line arguments:
- ``--junit``: If set, stores the test results in JUnit XML format and prints to `stdout` or
saves to a file if a filename is specified.
+- ``--summary``: If set, prints only the summary line for parsed test
+ results, rather than the result of every individual test. Does nothing
+ if ``--raw_output`` is set.
+
+- ``--failed``: If set, prints only the tests that failed or crashed, along
+ with the summary line, once all tests have run. Does nothing if
+ ``--raw_output`` is set.
+
- ``--filter``: Specifies filters on test attributes, for example, ``speed!=slow``.
Multiple filters can be used by wrapping input in quotes and separating filters
by commas. Example: ``--filter "speed>slow, module=example"``.
base-commit: c03c1a14507dfaf8b856c2608f9ac216021fc222
--
2.34.1
reply other threads:[~2026-10-20 14:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=179250646543.2190262.8632957027583518623@gmail.com \
--to=eugenio.zuccarelli@gmail.com \
--cc=brendan.higgins@linux.dev \
--cc=corbet@lwn.net \
--cc=david@davidgow.net \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=raemoar63@gmail.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
/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