netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Subject: [PATCH nft 1/8] tests: py: adapt this to new add element command semantics
Date: Mon, 29 Aug 2016 20:21:12 +0200	[thread overview]
Message-ID: <1472494879-16442-1-git-send-email-pablo@netfilter.org> (raw)

Since fd33d96 ("src: create element command"), add element doesn't
fail anymore if the element exists, you have to use create instead in
case you want to check if the element already exists.

Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
---
 tests/py/ip/sets.t  | 6 +++---
 tests/py/ip6/sets.t | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/tests/py/ip/sets.t b/tests/py/ip/sets.t
index 0e2b193..ee17d99 100644
--- a/tests/py/ip/sets.t
+++ b/tests/py/ip/sets.t
@@ -13,9 +13,9 @@
 !set1 type ipv4_addr;ok
 ?set1 192.168.3.4;ok
 
-?set1 192.168.3.4;fail
+?set1 192.168.3.4;ok
+?set1 192.168.3.5 192.168.3.6;ok
 ?set1 192.168.3.5 192.168.3.6;ok
-?set1 192.168.3.5 192.168.3.6;fail
 ?set1 192.168.3.8 192.168.3.9;ok
 ?set1 192.168.3.10 192.168.3.11;ok
 ?set1 1234:1234:1234:1234:1234:1234:1234:1234;fail
@@ -24,7 +24,7 @@
 !set2 type ipv4_addr;ok
 ?set2 192.168.3.4;ok
 ?set2 192.168.3.5 192.168.3.6;ok
-?set2 192.168.3.5 192.168.3.6;fail
+?set2 192.168.3.5 192.168.3.6;ok
 ?set2 192.168.3.8 192.168.3.9;ok
 ?set2 192.168.3.10 192.168.3.11;ok
 
diff --git a/tests/py/ip6/sets.t b/tests/py/ip6/sets.t
index ff38925..ea20834 100644
--- a/tests/py/ip6/sets.t
+++ b/tests/py/ip6/sets.t
@@ -13,12 +13,12 @@
 ?set2 192.168.3.4;fail
 !set2 type ipv6_addr;ok
 ?set2 1234:1234::1234:1234:1234:1234:1234;ok
-?set2 1234:1234::1234:1234:1234:1234:1234;fail
+?set2 1234:1234::1234:1234:1234:1234:1234;ok
 ?set2 1234::1234:1234:1234;ok
 ?set2 1234:1234:1234:1234:1234::1234:1234 1234:1234::123;ok
 ?set2 192.168.3.8 192.168.3.9;fail
 ?set2 1234:1234::1234:1234:1234:1234;ok
-?set2 1234:1234::1234:1234:1234:1234;fail
+?set2 1234:1234::1234:1234:1234:1234;ok
 ?set2 1234:1234:1234::1234;ok
 
 ip6 saddr @set2 drop;ok
-- 
2.1.4


             reply	other threads:[~2016-08-29 18:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29 18:21 Pablo Neira Ayuso [this message]
2016-08-29 18:21 ` [PATCH nft 2/8] src: add quota statement Pablo Neira Ayuso
2016-08-29 18:21 ` [PATCH nft 3/8] src: add numgen expression Pablo Neira Ayuso
2016-08-29 18:21 ` [PATCH nft 4/8] src: add hash expression Pablo Neira Ayuso
2016-08-29 18:21 ` [PATCH nft 5/8] evaluate: add expr_evaluate_integer() Pablo Neira Ayuso
2016-08-29 18:21 ` [PATCH nft 6/8] evaluate: validate maximum hash and numgen value Pablo Neira Ayuso
2016-08-29 18:21 ` [PATCH nft 7/8] parser_bison: add variable_expr rule Pablo Neira Ayuso
2016-08-29 18:21 ` [PATCH nft 8/8] parser_bison: allow variable references in set elements definition 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=1472494879-16442-1-git-send-email-pablo@netfilter.org \
    --to=pablo@netfilter.org \
    --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).