Netdev List
 help / color / mirror / Atom feed
From: Allison Henderson <achender@kernel.org>
To: netdev@vger.kernel.org, pabeni@redhat.com, edumazet@google.com,
	kuba@kernel.org, horms@kernel.org, linux-rdma@vger.kernel.org,
	achender@kernel.org, linux-kselftest@vger.kernel.org,
	shuah@kernel.org
Subject: [PATCH net-next v1 0/3] Log clean up and TAP follow ups
Date: Thu,  7 May 2026 16:32:10 -0700	[thread overview]
Message-ID: <20260507233213.556182-1-achender@kernel.org> (raw)

Hi all,

This is a follow up series to the  "Log collection, TAP compliance and
cleanups" set.  The sashiko report had made some points that I thought
was worth addressing.  This patch set fixes a few more TAP compliance
prints in the check_gcov* routines.  Also since the user must now pass
in the log folder to collect logs, log clean up is tightened to only
remove rds* prefixed artifacts instead of the entire folder.  Lastly a
the signal handler alarm should be disarmed after the completes to
avoid multiple calls to the stop_pcaps routine.

Questions, comments and feedback appreciated!

Thanks everyone!
Allison

Allison Henderson (3):
  selftests: rds: Fix stale log clean up
  selftests: rds: Fix TAP-prefixed prints in check_gcov*
  selftests: rds: Disarm signal alarm on test completion

 tools/testing/selftests/net/rds/run.sh  | 28 ++++++++++++++-----------
 tools/testing/selftests/net/rds/test.py | 10 ++++++++-
 2 files changed, 25 insertions(+), 13 deletions(-)

-- 
2.25.1


             reply	other threads:[~2026-05-07 23:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 23:32 Allison Henderson [this message]
2026-05-07 23:32 ` [PATCH net-next v1 1/3] selftests: rds: Fix stale log clean up Allison Henderson
2026-05-07 23:32 ` [PATCH net-next v1 2/3] selftests: rds: Fix TAP-prefixed prints in check_gcov* Allison Henderson
2026-05-07 23:32 ` [PATCH net-next v1 3/3] selftests: rds: Disarm signal alarm on test completion Allison Henderson
2026-05-10 17:30 ` [PATCH net-next v1 0/3] Log clean up and TAP follow ups patchwork-bot+netdevbpf

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=20260507233213.556182-1-achender@kernel.org \
    --to=achender@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox