From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Willy Tarreau <w@1wt.eu>, Zhangjin Wu <falcon@tinylab.org>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: nolibc: KTAP output and test reports
Date: Tue, 18 Jul 2023 09:31:06 +0200 [thread overview]
Message-ID: <c6d3cabb-84f9-4f00-bfdd-de6810ed4c99@t-8ch.de> (raw)
In-Reply-To: <cc03380f-594f-431b-941d-aea879a0c084@t-8ch.de>
Hi Willy,
On 2023-06-08 00:15:27+0200, Thomas Weißschuh wrote:
> after your recent discussions about the test output and report I
> wondered if it would make sense to switch nolibc-test to KTAP output
> format [0].
>
> With this it would be possible to have a wrapper script run each
> architecture test as its own test subcomponent.
> A (K)TAP parser/runner could then directly recognize and report failing
> testcases, making it easier to validate.
>
> Also maybe we can hook it up into the regular kselftests setup and have
> the bots run it as part of that.
>
> The kernel even includes a header-only library to implement the format [1].
> It also should be fairly easy to emit the format without a library.
Did you have a chance to look at this?
If you are not categorically opposed I would create a proof of concept
for further discussion.
> [0] Documentation/dev-tools/ktap.rst
> [1] Documentation/dev-tools/kselftest.rst (Test harness)
next prev parent reply other threads:[~2023-07-18 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 22:15 Thomas Weißschuh
2023-06-08 10:48 ` Zhangjin Wu
2023-07-18 7:31 ` Thomas Weißschuh [this message]
2023-07-18 17:14 ` Willy Tarreau
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=c6d3cabb-84f9-4f00-bfdd-de6810ed4c99@t-8ch.de \
--to=thomas@t-8ch.de \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=w@1wt.eu \
/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®