From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BA0BAEB64DD for ; Tue, 18 Jul 2023 07:31:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231719AbjGRHbV (ORCPT ); Tue, 18 Jul 2023 03:31:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44828 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231710AbjGRHbQ (ORCPT ); Tue, 18 Jul 2023 03:31:16 -0400 Received: from todd.t-8ch.de (todd.t-8ch.de [159.69.126.157]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 066381722; Tue, 18 Jul 2023 00:31:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=t-8ch.de; s=mail; t=1689665466; bh=kJctb5ztbgsw2RiDo1dH2gTWrFCAh3bUkwZf/e7KypM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=LYB1DGR6PNYW0upGLudBLi/cKArgBTGIl9aZ3lVh2+qBkBvpM6d9XzagjzkQk3wb9 CoYx1SFxWzovxjwM7I/nfcWumJ4yv6QlZ2ts5btwkPhMsanU/NUIo0m4KxOtq7+8L4 udTnzcagJobdKpG7DPC9cZMvSicwbUt7uYV/EukM= Date: Tue, 18 Jul 2023 09:31:06 +0200 From: Thomas =?utf-8?Q?Wei=C3=9Fschuh?= To: Willy Tarreau , Zhangjin Wu Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org Subject: Re: nolibc: KTAP output and test reports Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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)