All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, shuah@kernel.org,
	linux-kselftest@vger.kernel.org, Ido Schimmel <idosch@idosch.org>
Subject: Re: [PATCH net-next v2] selftests: net: add helper for checking if nettest is available
Date: Tue, 20 Aug 2024 08:44:12 -0700	[thread overview]
Message-ID: <20240820084412.4aa6abfb@kernel.org> (raw)
In-Reply-To: <ZsQLFwkNa-JnymGg@Laptop-X1>

On Tue, 20 Aug 2024 11:18:47 +0800 Hangbin Liu wrote:
> Excuse me, what's profile used here? I can't find the definition in
> Documentation/dev-tools/kselftest.rst.

Ah, sorry, I added timestamping output as a local patch for NIPA.

Random example:

TAP version 13
1..1
# overriding timeout to 7200
# selftests: net: amt.sh
# 13.15 [+13.15] TEST: amt discovery                                                 [ OK ]
# 16.27 [+3.12] TEST: IPv4 amt multicast forwarding                                 [ OK ]
# 19.14 [+2.86] TEST: IPv6 amt multicast forwarding                                 [ OK ]
# 670.88 [+651.74] TEST: IPv4 amt traffic forwarding torture                           [ OK ]
# 1203.28 [+532.40] TEST: IPv6 amt traffic forwarding torture                           [ OK ]
ok 1 selftests: net: amt.sh

It's not great, makes the lines longer and misaligned.
But it's helpful for debugging slow tests.

  reply	other threads:[~2024-08-20 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20  0:42 [PATCH net-next v2] selftests: net: add helper for checking if nettest is available Jakub Kicinski
2024-08-20  3:18 ` Hangbin Liu
2024-08-20 15:44   ` Jakub Kicinski [this message]
2024-08-21  1:21     ` Jakub Kicinski
2024-08-21  2:38       ` Hangbin Liu
2024-08-20 14:08 ` Ido Schimmel

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=20240820084412.4aa6abfb@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@idosch.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.