From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org,
linux-kselftest@vger.kernel.org, shuah@kernel.org,
Willem de Bruijn <willemb@google.com>
Subject: [PATCH net-next v5 1/3] selftests: net: py: support cmd verifying expected failure
Date: Mon, 27 Apr 2026 16:14:33 -0400 [thread overview]
Message-ID: <20260427201640.294694-2-willemdebruijn.kernel@gmail.com> (raw)
In-Reply-To: <20260427201640.294694-1-willemdebruijn.kernel@gmail.com>
From: Willem de Bruijn <willemb@google.com>
Support negative tests, where cmd raises an exception if the command
succeeded.
Existing fail values are
- True: Pass if returncode == 0, raise Exception otherwise
- False: Pass unconditionally
- None: True iff not terminated explicitly
Introduce a variant of True that inverses the condition:
- 'verify_failed': Pass if returncode != 0, raise Exception otherwise
We cannot reuse False for this, because existing tests rely on current
behavior to pass unconditionally.
Only suppress regular test failure. Python subprocess may set a
negative return code on process crash or timeout. Those are not
anticipated failures.
Signed-off-by: Willem de Bruijn <willemb@google.com>
---
tools/testing/selftests/net/lib/py/utils.py | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/net/lib/py/utils.py b/tools/testing/selftests/net/lib/py/utils.py
index 6c44a3d2bbf7..ef31c0ba47fc 100644
--- a/tools/testing/selftests/net/lib/py/utils.py
+++ b/tools/testing/selftests/net/lib/py/utils.py
@@ -111,10 +111,14 @@ class cmd:
stdout, stderr = self._process_terminate(terminate=terminate,
timeout=timeout)
- if self.proc.returncode != 0 and fail:
+
+ if (self.proc.returncode != 0 and fail and
+ (self.proc.returncode < 0 or fail != 'verify_failed')):
if len(stderr) > 0 and stderr[-1] == "\n":
stderr = stderr[:-1]
raise CmdExitFailure("Command failed", self)
+ elif self.proc.returncode == 0 and fail == 'verify_failed':
+ raise CmdExitFailure("Command succeeded while should fail", self)
def __repr__(self):
def str_fmt(name, s):
--
2.54.0.545.g6539524ca2-goog
next prev parent reply other threads:[~2026-04-27 20:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 20:14 [PATCH net-next v5 0/3] selftests: drv-net: convert so_txtime to drv-net Willem de Bruijn
2026-04-27 20:14 ` Willem de Bruijn [this message]
2026-04-27 20:14 ` [PATCH net-next v5 2/3] selftests: net: py: add tc utility Willem de Bruijn
2026-04-27 20:14 ` [PATCH net-next v5 3/3] selftests: drv-net: convert so_txtime to drv-net Willem de Bruijn
2026-04-27 22:48 ` [PATCH net-next v5 0/3] " Jakub Kicinski
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=20260427201640.294694-2-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=willemb@google.com \
/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