From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: David Gow <david@davidgow.net>
Cc: Brendan Higgins <brendan.higgins@linux.dev>,
Rae Moar <raemoar63@gmail.com>, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kunit: tool: Recommend --raw_output=all if no KTAP found
Date: Fri, 27 Feb 2026 16:46:44 +0200 [thread overview]
Message-ID: <aaGuVA4q5BXSxBWX@ashevche-desk.local> (raw)
In-Reply-To: <20260227105650.307845-1-david@davidgow.net>
On Fri, Feb 27, 2026 at 06:56:49PM +0800, David Gow wrote:
> If no KTAP header is found in the kernel output (e.g., because the kernel
> crashed before the KUnit executor was run), it's very useful to re-run the
> test with --raw_output=all, as that will show any error output (such as a
> stacktrace, log message, BUG, etc). This is not particularly intuitive,
> however, as --raw_output=all is not well known.
>
> Add an extra log line to advertise --raw_output=all in this case, as it's
> a terrible user experience to just get "Did any KUnit tests run?"
What's the difference to "full"?
Thanks for adding this, btw!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-27 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 10:56 David Gow
2026-02-27 14:46 ` Andy Shevchenko [this message]
2026-02-28 10:11 ` David Gow
2026-02-28 10:44 ` Andy Shevchenko
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=aaGuVA4q5BXSxBWX@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--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=shuah@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
all inboxes | Powered by JetHome®