netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@kernel.org>
To: netdev@vger.kernel.org
Cc: kuba@kernel.org, David Ahern <dsahern@kernel.org>
Subject: [PATCH net-next 0/3] selftests: Updates to fcnal-test for autoamted environment
Date: Wed, 24 Jan 2024 14:41:14 -0700	[thread overview]
Message-ID: <20240124214117.24687-1-dsahern@kernel.org> (raw)

The first patch updates the PATH for fcnal-test.sh to find the nettest
binary when invoked at the top-level directory via 
   make -C tools/testing/selftests TARGETS=net run_tests

Second patch fixes a bug setting the ping_group; it has a compound value
and that value is not traversing the various helper functions in tact.
Fix by creating a helper specific to setting it.

Third patch adds more output when a test fails - e.g., to catch a change
in the return code of some test.

With these 3 patches, the entire suite completes successfully when
run on Ubuntu 23.10 with 6.5 kernel - 914 tests pass, 0 fail.
 
David Ahern (3):
  selftest: Update PATH for nettest in fcnal-test
  selftest: Fix set of ping_group_range in fcnal-test
  selftest: Show expected and actual return codes for test failures in
    fcnal-test

 tools/testing/selftests/net/fcnal-test.sh | 25 +++++++++++++++++------
 1 file changed, 19 insertions(+), 6 deletions(-)

-- 
2.39.3 (Apple Git-145)


             reply	other threads:[~2024-01-24 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 21:41 David Ahern [this message]
2024-01-24 21:41 ` [PATCH net-next 1/3] selftest: Update PATH for nettest in fcnal-test David Ahern
2024-01-24 21:41 ` [PATCH net-next 2/3] selftest: Fix set of ping_group_range " David Ahern
2024-01-24 21:41 ` [PATCH net-next 3/3] selftest: Show expected and actual return codes for test failures " David Ahern
2024-01-26  1:20 ` [PATCH net-next 0/3] selftests: Updates to fcnal-test for autoamted environment 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=20240124214117.24687-1-dsahern@kernel.org \
    --to=dsahern@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).