mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
	"Shuah Khan" <shuah@kernel.org>,
	"Bird, Timothy" <Tim.Bird@sony.com>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] selftests/timens: Print TAP headers
Date: Wed, 7 May 2025 15:06:16 -0600	[thread overview]
Message-ID: <5609c6de-e5cf-4f6d-8412-71149fae2580@linuxfoundation.org> (raw)
In-Reply-To: <20250502-selftests-timens-fixes-v1-1-fb517c76f04d@linutronix.de>

On 5/2/25 06:03, Thomas Weißschuh wrote:
> The TAP specification requires that the output begins with a header line.
> These headers lines are missing in the timens tests.
> 
> Print such a line.

There is no cover letter for this - so I will respond to the first
patch. The TAP information is added by the kselftest wrapper if
you were to run the test using ksefltest.

The following will add the TAP header or if you use make kselftest
command from the main Makefile.

make -C timens run_tests

cd timens; make run_tests (will also add TAP header)

The only time you won't see the TAP headers is when you run the test
from the test directory just as a command. Is this what you need
to do? I would rather not see TAP headers added to invidual tests
unless there is a good reason for it.

The problem with adding TAP headers is two-fold:

1. It becomes hard to read the ouptput if test is run using
    the framework a. make -C timens run_tests b. cd timens; make run_tests
2. These headers become bested and TAP doesn't like nested TAP headers.
    My undestansing is parses will have problems.

I am adding Tim Bird to the discussion.

Tim, is this still an issue? Are nested TAP headers still a problem.

Even if they aren't there is the issue of multiple TAP headers for
each test when we run the test using framework.

thanks,
-- Shuah

  parent reply	other threads:[~2025-05-07 21:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02 12:03 [PATCH 0/3] selftests/timens: Various small fixes Thomas Weißschuh
2025-05-02 12:03 ` [PATCH 1/3] selftests/timens: Print TAP headers Thomas Weißschuh
2025-05-02 12:13   ` Muhammad Usama Anjum
2025-05-07 21:06   ` Shuah Khan [this message]
2025-05-09 15:41     ` Thomas Weißschuh
2025-05-09 18:53       ` Shuah Khan
2025-05-09 19:07       ` Kees Cook
2025-05-02 12:03 ` [PATCH 2/3] selftests/timens: Make run_tests() functions static Thomas Weißschuh
2025-05-02 12:13   ` Muhammad Usama Anjum
2025-05-02 12:03 ` [PATCH 3/3] selftests/timens: timerfd: Use correct clockid type in tclock_gettime() Thomas Weißschuh
2025-05-02 12:14   ` Muhammad Usama Anjum

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=5609c6de-e5cf-4f6d-8412-71149fae2580@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=Tim.Bird@sony.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=thomas.weissschuh@linutronix.de \
    /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®