Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 18 Jul 2023 09:31:06 +0200
From:   Thomas =?utf-8?Q?Wei=C3=9Fschuh?= <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
Message-ID: <c6d3cabb-84f9-4f00-bfdd-de6810ed4c99@t-8ch.de>
References: <cc03380f-594f-431b-941d-aea879a0c084@t-8ch.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <cc03380f-594f-431b-941d-aea879a0c084@t-8ch.de>
Precedence: bulk

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)