From: Florian Westphal <fw@strlen.de>
To: Thomas Haller <thaller@redhat.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
NetFilter <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH nft 1/1] tests/shell: add NFT_TEST_FAIL_ON_SKIP_EXCEPT for allow-list of skipped tests (XFAIL)
Date: Thu, 19 Oct 2023 11:20:32 +0200 [thread overview]
Message-ID: <20231019092032.GA2230@breakpoint.cc> (raw)
In-Reply-To: <651666347a414eecbb11ad97d6a75a0e1a401bf3.camel@redhat.com>
Thomas Haller <thaller@redhat.com> wrote:
> Unless you think, that the current SKIP mechanism (feature
> detection/probing) in master is 100% reliable, and there is no need to
> worry about SKIP hiding a bug.
Yes, I do not worry about SKIP, because I never see a SKIP *unless*
I run the test suite on an old kernel.
"Old" here means 5.14.y or so.
prev parent reply other threads:[~2023-10-19 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 22:33 [PATCH nft 1/1] tests/shell: add NFT_TEST_FAIL_ON_SKIP_EXCEPT for allow-list of skipped tests (XFAIL) Thomas Haller
2023-10-18 9:33 ` Pablo Neira Ayuso
2023-10-18 11:40 ` Thomas Haller
2023-10-19 9:20 ` Florian Westphal [this message]
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=20231019092032.GA2230@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=thaller@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;
as well as URLs for NNTP newsgroup(s).