From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft,v3] tests: shell: fix spurious errors in sets/0036add_set_element_expiration_0
Date: Thu, 28 Sep 2023 21:17:20 +0200 [thread overview]
Message-ID: <ZRXRQO44pxHRa53x@calendula> (raw)
In-Reply-To: <ZRWUpn963dk3Eaey@orbyte.nwl.cc>
On Thu, Sep 28, 2023 at 04:58:46PM +0200, Phil Sutter wrote:
> On Wed, Sep 27, 2023 at 06:39:37PM +0200, Pablo Neira Ayuso wrote:
> > A number of changes to fix spurious errors:
> >
> > - Add seconds as expiration, otherwise 14m59 reports 14m in minute
> > granularity, this ensures suficient time in a very slow environment with
> > debugging instrumentation.
> >
> > - Provide expected output.
> >
> > - Update sed regular expression to make 'ms' optional and use -E mode.
> >
> > Fixes: adf38fd84257 ("tests: shell: use minutes granularity in sets/0036add_set_element_expiration_0")
> > Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> > ---
> > v3: - [ "$test_output" != "$EXPECTED" ], not [ "$test_output" != "$RULESET" ]
> > - Make 'ms' optional in sed regular expression
> > - Use -E in sed
> >
> > .../testcases/sets/0036add_set_element_expiration_0 | 10 +++++++---
> > 1 file changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/tests/shell/testcases/sets/0036add_set_element_expiration_0 b/tests/shell/testcases/sets/0036add_set_element_expiration_0
> > index 12f10074409f..0fd016e9f857 100755
> > --- a/tests/shell/testcases/sets/0036add_set_element_expiration_0
> > +++ b/tests/shell/testcases/sets/0036add_set_element_expiration_0
> > @@ -3,17 +3,21 @@
> > set -e
> >
> > drop_seconds() {
> > - sed 's/m[0-9]*s[0-9]*ms/m/g'
> > + sed -E 's/m[0-9]*s([0-9]*ms)?/m/g'
> > }
>
> So sometimes there's no ms part in output. In theory one would have to
> make the seconds part optional, too. Funny how tedious these little
> things may become to fix.
>
> Anyway, it should work without -E by escaping braces and the question
> mark. But accoring to sed(1), -E is in POSIX meanwhile so no big deal.
>
> > RULESET="add table ip x
> > +add set ip x y { type ipv4_addr; flags dynamic,timeout; }
> > +add element ip x y { 1.1.1.1 timeout 30m expires 15m59s }"
> > +
> > +EXPECTED="add table ip x
> > add set ip x y { type ipv4_addr; flags dynamic,timeout; }
> > add element ip x y { 1.1.1.1 timeout 30m expires 15m }"
>
> I would have piped RULESET through drop_seconds in the $DIFF call below,
> but this variant surely saves a few cycles. :D
I am useless. I quickly tried this, but echo disregards newlines,
triggering a mismatch in the diff, perhaps printf can address this.
I just wanted to make this reliable, it has been bothering me in my
test infrastructure which is running this in a loop and occasionally
triggering this false positive.
next prev parent reply other threads:[~2023-09-28 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 16:39 [PATCH nft,v3] tests: shell: fix spurious errors in sets/0036add_set_element_expiration_0 Pablo Neira Ayuso
2023-09-28 14:58 ` Phil Sutter
2023-09-28 19:17 ` Pablo Neira Ayuso [this message]
2023-09-29 9:49 ` Phil Sutter
2023-09-29 9:53 ` Pablo Neira Ayuso
2023-09-29 10:37 ` Phil Sutter
2023-09-29 10:54 ` 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=ZRXRQO44pxHRa53x@calendula \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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).