From: Thomas Haller <thaller@redhat.com>
To: Florian Westphal <fw@strlen.de>
Cc: NetFilter <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH nft 2/2] tests/shell: add missing ".nodump" file for tests without dumps
Date: Fri, 08 Sep 2023 12:42:57 +0200 [thread overview]
Message-ID: <65b038a11c1168a829a19e309bd174a9e01ae2d1.camel@redhat.com> (raw)
In-Reply-To: <20230908102226.GA6592@breakpoint.cc>
On Fri, 2023-09-08 at 12:22 +0200, Florian Westphal wrote:
> Thomas Haller <thaller@redhat.com> wrote:
> > These files are generated by running `./tests/shell/run-tests.sh -
> > g`.
> > Commit the .nodump files to git.
> >
> > The point is that we can in the future run `./tests/shell/run-
> > tests.sh
> > -g` and don't get an abundance of irrelevant dump files generated.
> >
> > This raises the question, whether some of these tests should
> > actually
> > have their ruleset compared against a .nft file. But this is
> > nothing
> > new and not prevented by this change. The change merely expresses
> > in
> > clear way that those tests are (currently) meant not to have .nft
> > files.
>
> I think it would be preferrable to have a patch 2/3 that first adds
> new .nft dump files for all tests where the output is stable, and
> then
> only add the .nodump files (this patch) for those where dump
> validation
> cannot work.
>
> I suspect that most will pass as expected.
> Even an empty dump file can be useful because this would catch
> (unlikely) bugs with delete/flush failure.
>
> We could simplify some scripts later on, some of the no-dump scripts
> manually validate output, that isn't needed anymore after this.
>
Makes sense. Will do.
Thomas
prev parent reply other threads:[~2023-09-08 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 21:05 [PATCH nft 1/2] tests/shell: honor .nodump file for tests without nft dumps Thomas Haller
2023-09-07 21:05 ` [PATCH nft 2/2] tests/shell: add missing ".nodump" file for tests without dumps Thomas Haller
2023-09-08 10:22 ` Florian Westphal
2023-09-08 10:42 ` Thomas Haller [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=65b038a11c1168a829a19e309bd174a9e01ae2d1.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).