From: Florian Westphal <fw@strlen.de>
To: Yi Chen <yiche@redhat.com>
Cc: pablo@netfilter.org, phil@nwl.cc, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] test: shell: run-test.sh: introduce NFT_TEST_EXCLUDES
Date: Wed, 4 Feb 2026 16:06:07 +0100 [thread overview]
Message-ID: <aYNgX-nh04sAQdU8@strlen.de> (raw)
In-Reply-To: <20260204144940.63422-1-yiche@redhat.com>
Yi Chen <yiche@redhat.com> wrote:
> Introduce the NFT_TEST_EXCLUDES environment variable to allow excluding
> one or more specific test cases.
> This is useful for some releases where certain tests are not yet supported.
> allowing them to be skipped directly in the test script
> without modifying the run-test.sh itself.
Wouldn't it make more sense to add a feature test for those?
Or is this about test cases that fail because of a real bug that
where the fix wasn't backported yet?
next prev parent reply other threads:[~2026-02-04 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 14:49 [PATCH] test: shell: run-test.sh: introduce NFT_TEST_EXCLUDES Yi Chen
2026-02-04 15:06 ` Florian Westphal [this message]
2026-02-05 2:03 ` Yi Chen
2026-02-05 2:10 ` Florian Westphal
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=aYNgX-nh04sAQdU8@strlen.de \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
--cc=yiche@redhat.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