netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Thomas Haller <thaller@redhat.com>
Cc: NetFilter <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH nft 1/3] tests/shell: add "bogons/nft-f/zero_length_devicename2_assert"
Date: Tue, 24 Oct 2023 12:24:06 +0200	[thread overview]
Message-ID: <ZTebRvOP2pEoHsV+@calendula> (raw)
In-Reply-To: <24637db2fe827e321ea152b5b24cfa3a29d3660d.camel@redhat.com>

On Tue, Oct 24, 2023 at 12:15:22PM +0200, Thomas Haller wrote:
> On Tue, 2023-10-24 at 11:57 +0200, Pablo Neira Ayuso wrote:
> > Series aplied, thanks.
> 
> Thank you.
> 
> > 
> > After all these updates I see this failure:
> > 
> > W: [FAILED]     1/1 testcases/sets/elem_opts_compat_0
> > 
> > I: results: [OK] 0 [SKIPPED] 0 [FAILED] 1 [TOTAL] 1
> > 
> > when running tests.
> > 
> 
> Hm. I don't get such failure (Kernel 6.5.6-200.fc38.x86_64).
> But regardless of that, I don't think that my patches had anything to
> do with that test, do they?
> 
> 
> Can you provide more information? Can you bisect the failure?
> 
> Could you share:
> 
>   make && ./tests/shell/run-tests.sh ./tests/shell/testcases/sets/elem_opts_compat_0 -x -k
>   grep -R ^ /tmp/nft-test.latest.*/

/tmp/nft-test.latest.root/times:2.3
/tmp/nft-test.latest.root/times:3067.20
/tmp/nft-test.latest.root/times:3069.50
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/times:0.12
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/times:3069.38
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/times:3069.50
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/ruleset-after:table ip t {
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/ruleset-after:       set s {
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/ruleset-after:               type inet_service
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/ruleset-after:               counter
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/ruleset-after:               timeout 30s
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/ruleset-after:       }
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/ruleset-after:}
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/rc-failed:2
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/name:testcases/sets/elem_opts_compat_0
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/testout.log:Command: testcases/sets/elem_opts_compat_0 
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/testout.log:testcases/sets/elem_opts_compat_0: 20: Syntax error: redirection unexpected
/tmp/nft-test.latest.root/test-testcases-sets-elem_opts_compat_0.1/rc-failed-exit:2

  reply	other threads:[~2023-10-24 10:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 17:00 [PATCH nft 1/3] tests/shell: add "bogons/nft-f/zero_length_devicename2_assert" Thomas Haller
2023-10-23 17:00 ` [PATCH nft 2/3] tests/shell: cover long interface name in "0042chain_variable_0" test Thomas Haller
2023-10-23 17:00 ` [PATCH nft 3/3] parser_bison: fix length check for ifname in ifname_expr_alloc() Thomas Haller
2023-10-23 17:15   ` Pablo Neira Ayuso
2023-10-23 17:16     ` Pablo Neira Ayuso
2023-10-23 17:33       ` Thomas Haller
2023-10-24  9:57 ` [PATCH nft 1/3] tests/shell: add "bogons/nft-f/zero_length_devicename2_assert" Pablo Neira Ayuso
2023-10-24 10:15   ` Thomas Haller
2023-10-24 10:24     ` Pablo Neira Ayuso [this message]
2023-10-24 10:29       ` Florian Westphal
2023-10-24 10:43         ` Pablo Neira Ayuso
2023-10-24 11:50         ` Phil Sutter

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=ZTebRvOP2pEoHsV+@calendula \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=thaller@redhat.com \
    /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).