From: Kees Cook <kees@kernel.org>
To: David Gow <david@davidgow.net>
Cc: "Brendan Higgins" <brendan.higgins@linux.dev>,
"Rae Moar" <raemoar63@gmail.com>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
kunit-dev@googlegroups.com, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: [PATCH v4 1/2] kunit: tool: Parse and print the reason tests are skipped
Date: Wed, 10 Jun 2026 13:27:07 -0700 [thread overview]
Message-ID: <202606101326.DD12C7CC@keescook> (raw)
In-Reply-To: <20260606013827.240790-1-david@davidgow.net>
On Sat, Jun 06, 2026 at 09:38:17AM +0800, David Gow wrote:
> When a KUnit test (or other KTAP test) is skipped, a "skip reason" can be
> provided. kunit.py has never done anything with this, ignoring anything
> included in the KTAP output after the 'SKIP' directive.
>
> Since we have it, and it's used, print it in a nice friendly yellow in
> parentheses after a skipped test's name.
>
> (And, by parsing it, it can be included in the JUnit results as well.)
>
> Signed-off-by: David Gow <david@davidgow.net>
Thank you; this makes my life easier so I don't have to use --raw_output
in my fortify testing. :)
Reviewed-by: Kees Cook <kees@kernel.org>
--
Kees Cook
prev parent reply other threads:[~2026-06-10 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 1:38 [PATCH v4 1/2] kunit: tool: Parse and print the reason tests are skipped David Gow
2026-06-06 1:38 ` [PATCH v4 2/2] kunit: tool: Add (primitive) support for outputting JUnit XML David Gow
2026-06-10 20:27 ` Kees Cook [this message]
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=202606101326.DD12C7CC@keescook \
--to=kees@kernel.org \
--cc=brendan.higgins@linux.dev \
--cc=david@davidgow.net \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=raemoar63@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=thomas.weissschuh@linutronix.de \
--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