From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: "open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>
Cc: Shuah Khan <shuah@kernel.org>,
pablo@netfilter.org, fw@strlen.de, jeffrin@rajagiritech.edu.in,
horms@verge.net.au, yanhaishuang@cmss.chinamobile.com,
lkft-triage@lists.linaro.org
Subject: selftests:netfilter: nft_nat.sh: internal00-0 Error Could not open file \"-\" No such file or directory
Date: Tue, 26 Nov 2019 09:25:00 +0530 [thread overview]
Message-ID: <CA+G9fYtgEfa=bq5C8yZeF6P563Gw3Fbs+-h_oy1e4G_1G0jrgw@mail.gmail.com> (raw)
Do you see the following error while running selftests netfilter
nft_nat.sh test ?
Are we missing any kernel config fragments ? We are merging configs
from the directory.
# selftests netfilter nft_nat.sh
netfilter: nft_nat.sh_ #
# Cannot create namespace file \"/var/run/netns/ns1\" File exists
create: namespace_file #
# internal00-0 Error Could not open file \"-\" No such file or directory
Error: Could_not #
#
: _ #
#
: _ #
# internal00-0 Error Could not open file \"-\" No such file or directory
Error: Could_not #
#
: _ #
#
: _ #
# internal00-0 Error Could not open file \"-\" No such file or directory
Error: Could_not #
#
: _ #
#
: _ #
# <cmdline>16-12 Error syntax error, unexpected counter
Error: syntax_error, #
# list counter inet filter ns0in
counter: inet_filter #
# ^^^^^^^
: _ #
# ERROR ns0in counter in ns1 has unexpected value (expected packets 1 bytes 84)
ns0in: counter_in #
# <cmdline>16-12 Error syntax error, unexpected counter
Error: syntax_error, #
# list counter inet filter ns0in
counter: inet_filter #
# ^^^^^^^
: _ #
# <cmdline>16-12 Error syntax error, unexpected counter
Full test log:
https://lkft.validation.linaro.org/scheduler/job/1021542#L14602
https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20191125/testrun/1021542/log
Dashboard link,
https://qa-reports.linaro.org/lkft/linux-mainline-oe/tests/kselftest/netfilter_nft_nat.sh
https://qa-reports.linaro.org/lkft/linux-next-oe/tests/kselftest/netfilter_nft_nat.sh
metadata:
git branch: master
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git commit: c165016bac2719e05794c216f9b6da730d68d1e3
git describe: next-20191125
make_kernelversion: 5.4.0-rc8
kernel-config:
http://snapshots.linaro.org/openembedded/lkft/lkft/sumo/hikey/lkft/linux-next/653/config
build-location:
http://snapshots.linaro.org/openembedded/lkft/lkft/sumo/hikey/lkft/linux-next/653
Best regards
Naresh Kamboju
next reply other threads:[~2019-11-26 3:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 3:55 Naresh Kamboju [this message]
2019-11-26 15:56 ` selftests:netfilter: nft_nat.sh: internal00-0 Error Could not open file \"-\" No such file or directory Florian Westphal
[not found] ` <20191127001931.GA3717@debian>
2019-11-27 12:45 ` Jeffrin Thalakkottoor
2019-11-27 12:48 ` Jeffrin Thalakkottoor
2019-11-27 19:19 ` Naresh Kamboju
2019-11-27 22:05 ` Florian Westphal
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='CA+G9fYtgEfa=bq5C8yZeF6P563Gw3Fbs+-h_oy1e4G_1G0jrgw@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=fw@strlen.de \
--cc=horms@verge.net.au \
--cc=jeffrin@rajagiritech.edu.in \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=shuah@kernel.org \
--cc=yanhaishuang@cmss.chinamobile.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).