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 5B1C4C6FD1C for ; Mon, 20 Mar 2023 19:30:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229869AbjCTTaJ (ORCPT ); Mon, 20 Mar 2023 15:30:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37756 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229940AbjCTT3W (ORCPT ); Mon, 20 Mar 2023 15:29:22 -0400 Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 674562CFF5 for ; Mon, 20 Mar 2023 12:21:32 -0700 (PDT) Received: by mail-pl1-x629.google.com with SMTP id iw3so13631850plb.6 for ; Mon, 20 Mar 2023 12:21:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; t=1679340081; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=BWhumSwE6VPdraIKdHkGXCZdveSGyvkn+v17HrXzLoU=; b=VA8aZkWAwouurkFwtG7y1H2ErfKKJZWtd5n6zNvgQ9V/tbgcrFvDEjgNUX+C26EohC 3XF5OzB3GuMYennO2skytyBQ67dXiOz+J+yRqnA0MTaIA4ZL73XFzQi6B28vNZkxeOXv SrA2p2w4nBtJd+CgCfvqhSJuIht0fkWs9DLQWukwKJRNHBZjGgTFM6EmIFbFYTV/zUUZ yDDInIgClxY2cZgPPnHMzu/Q0lSWerxNkwn2AMN2T8lFZY588uwPLVtlLM9GAuqaanZc ue3b4QlswNx2ohsNZ0GpI3MomRMNsK3/20Lf+pC9STW4HMJPDhF7hsuAGTxEJC73c8xZ xLMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679340081; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=BWhumSwE6VPdraIKdHkGXCZdveSGyvkn+v17HrXzLoU=; b=ddAfUhMgzqjBehoEq+5pVSSyAFRFqE1NCChXQbT+vG9kq0b5h37Mide7rWjnVt7J7o wbmWzmcagM7R3JtK1hPIyFjm5OvWoeLwbAkPTRneXCiQ1zG9aPsHf6Bfc7UT1iBGpL6M saI5roshMBNQyoIo7Bn5awiASH3yHZCuwXEpJSI3+EbfQzxYq6znmP+x+qcccXSOuEZz ACsOrh2HRnybeTF3DvBI3BPwCUVKw0cmtP5c1ajynca+SnmcxafYOQEiqegfCLgxu2cB EmrckXT6/44FD+2AiCue4qzPulQnlWY6zX1266zJw6WtQdhMF9zs1rtUGl2NkQ2NiHO+ O5dA== X-Gm-Message-State: AO0yUKUD/fl50cwO49QA0D34fgKRBCkx8JlHr/s5az8M0lezIu0Wq11L aYKNwMBIv/kKs4nlnOY+K3BOP68TwNGXkpE3yNnhEQ== X-Google-Smtp-Source: AK7set97ym3r3TVpdTad4XjDZPrMBp8LWDpdIFqTUCzJk9uiQxZ8zofvh8E3jDnD5nKC5aWGXAkBO7iJddRY68bTF8Q= X-Received: by 2002:a17:902:c94f:b0:1a0:527b:9189 with SMTP id i15-20020a170902c94f00b001a0527b9189mr6877966pla.11.1679340080664; Mon, 20 Mar 2023 12:21:20 -0700 (PDT) MIME-Version: 1.0 References: <20230316225915.494688-1-rmoar@google.com> In-Reply-To: <20230316225915.494688-1-rmoar@google.com> From: Daniel Latypov Date: Mon, 20 Mar 2023 12:21:09 -0700 Message-ID: Subject: Re: [KTAP V2 PATCH] ktap_v2: add recognized test name line To: Rae Moar Cc: frowand.list@gmail.com, davidgow@google.com, skhan@linuxfoundation.org, keescook@chromium.org, Tim.Bird@sony.com, brendanhiggins@google.com, corbet@lwn.net, guillaume.tucker@collabora.com, kernelci@lists.linux.dev, kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 16, 2023 at 3:59=E2=80=AFPM Rae Moar wrote: > > Add recognition of the test name line ("# Subtest: ") to the KTAP v= 2 > spec. > > The purpose of this line is to declare the name of a test before its > results. This functionality is especially useful when trying to parse tes= t > results incrementally and when interpretting results after a crash. > > This line is already compliant with KTAP v1 as it is interpretted as a minor nit for if there's a v2, s/interprett/interpret (here and above) Also, I want to elaborate on the previous paragraph a bit more, in case the motivation isn't clear. The problem with TAP and KTAP as-is is that the name of a test case is only known *after* it completes. So the scenario being referred to is KTAP version 1 1..1 It would be nice if parsers could report "test FOO caused a crash" as opposed to "the first test case caused a crash, good luck figuring out which one that was" Daniel