From: Thomas Haller <thaller@redhat.com>
To: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft 1/5] tests: add feature probing
Date: Wed, 06 Sep 2023 16:36:02 +0200 [thread overview]
Message-ID: <04c202a04375dd46b4899d02b4683f055edcba29.camel@redhat.com> (raw)
In-Reply-To: <20230904090640.3015-2-fw@strlen.de>
On Mon, 2023-09-04 at 11:06 +0200, Florian Westphal wrote:
> Running selftests on older kernels makes some of them fail very early
> because some tests use features that are not available on older
> kernels, e.g. -stable releases.
>
> Known examples:
> - inner header matching
> - anonymous chains
> - elem delete from packet path
>
> Also, some test cases might fail because a feature isn't
> compiled in, such as netdev chains for example.
>
> This adds a feature-probing to the shell tests.
On my Fedora 38, I have currently 7 tests failing.
With this patchset, tests/shell/testcases/maps/typeof_maps_add_delete
is now skipped (6 failing left).
Nice!
> +check_features()
> +{
> + for ffilename in $TESTDIR/../features/*.nft; do
> + feature=$(basename $ffilename)
> +
> + feature=${feature#*/}
> + feature=${feature%*.nft}
> +
> + eval NFT_HAVE_${feature}=0
> + $NFT --check -f "$ffilename" 2>/dev/null
> + if [ $? -eq 0 ]; then
> + eval NFT_HAVE_${feature}=1
the existing variables like VERBOSE,VALGRIND use "y" for true and
everything else is false.
I think 0|1 looks better. But it should be consistent. If 0|1 is used,
the other variables should be adjusted.
Note that on the other branch I added normalization functions
bool_y()/bool_n() to accept values like true/1/y/yes from the user, and
normalize to y|n. This could be changed internally to 1|0 without
breaking user setups.
> for testfile in $(find_tests)
> @@ -277,5 +296,10 @@ check_kmemleak_force
>
> msg_info "results: [OK] $ok [FAILED] $failed [TOTAL] $((ok+failed))"
>
> +if [ "$VERBOSE" == "y" ] ; then
> + echo "Probed Features:"
> + env | grep NFT_HAVE_
> +fi
xxx=$'\nNFT_HAVE_XXXXX=bogus' ./tests/shell/run-tests.sh /bin/true -v
gives the wrong output. Could be instead:
for v in $(compgen -v | grep '^NFT_HAVE_') ; do
echo "$v=${!v}";
done
next prev parent reply other threads:[~2023-09-06 14:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 9:06 [PATCH nft 0/5] tests: shell: add and use feature probing Florian Westphal
2023-09-04 9:06 ` [PATCH nft 1/5] tests: add " Florian Westphal
2023-09-05 13:00 ` Phil Sutter
2023-09-05 13:44 ` Florian Westphal
2023-09-05 14:01 ` Phil Sutter
2023-09-05 14:09 ` Florian Westphal
2023-09-05 20:28 ` Phil Sutter
2023-09-06 5:17 ` Thomas Haller
2023-09-06 14:36 ` Thomas Haller [this message]
2023-09-04 9:06 ` [PATCH nft 2/5] tests: shell: let netdev_chain_0 test indicate SKIP if kernel requires netdev device Florian Westphal
2023-09-05 13:03 ` Phil Sutter
2023-09-06 13:42 ` Thomas Haller
2023-09-04 9:06 ` [PATCH nft 3/5] tests: shell: typeof_integer/raw: prefer @nh for payload matching Florian Westphal
2023-09-04 9:06 ` [PATCH nft 4/5] tests: shell: add and use feature probe for map query like a set Florian Westphal
2023-09-06 14:39 ` Thomas Haller
2023-09-04 9:06 ` [PATCH nft 5/5] tests: shell skip inner matching tests if unsupported 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=04c202a04375dd46b4899d02b4683f055edcba29.camel@redhat.com \
--to=thaller@redhat.com \
--cc=fw@strlen.de \
--cc=netfilter-devel@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).