From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Subject: [PATCH nft 0/3] json: resolve multiple test case failures
Date: Tue, 3 Nov 2020 19:20:37 +0100 [thread overview]
Message-ID: <20201103182040.24858-1-fw@strlen.de> (raw)
Over the last few months nft gained a few new features and test cases
that either do not have a json test case or fail in json mode.
First two patches only touch the test cases themselves, but the snat.t
failure turned out to be due to lack of feature parity with the normal
bison parser.
Thus that patch adds needed export/import facility for nat_type
and the netmap flag.
src/json.c | 43 +++++++++++++---
src/parser_json.c | 70 +++++++++++++++++++++++++-
tests/py/bridge/reject.t | 2
tests/py/bridge/reject.t.json | 72 +++++++++++++++++++++++++++
tests/py/inet/dnat.t | 4 -
tests/py/inet/dnat.t.json | 55 ++++++++++++++++++++
tests/py/inet/sets.t.json | 74 ++++++++++++++++++++++++++++
tests/py/ip/icmp.t.json | 4 -
tests/py/ip/icmp.t.json.output | 2
tests/py/ip/snat.t.json | 108 +++++++++++++++++++++++++++++++++++++++++
10 files changed, 418 insertions(+), 16 deletions(-)
next reply other threads:[~2020-11-03 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 18:20 Florian Westphal [this message]
2020-11-03 18:20 ` [PATCH nft 1/3] tests: json: add missing test case output Florian Westphal
2020-11-03 18:20 ` [PATCH nft 2/3] tests: avoid warning and add missing json test cases Florian Westphal
2020-11-03 18:20 ` [PATCH nft 3/3] json: add missing nat_type flag and netmap nat flag Florian Westphal
2020-11-04 13:03 ` [PATCH nft 0/3] json: resolve multiple test case failures Pablo Neira Ayuso
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=20201103182040.24858-1-fw@strlen.de \
--to=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).