From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: LTP List <ltp@lists.linux.it>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"vadimp@nvidia.com" <vadimp@nvidia.com>,
idosch@nvidia.com, Raju.Lakkaraju@microchip.com, jiri@nvidia.com
Subject: [next] LTP: netns_breakns: Command \"add\" is unknown, try \"ip link help\".
Date: Thu, 21 Apr 2022 18:12:54 +0530 [thread overview]
Message-ID: <CA+G9fYvO5OERA0k-r=Q8gbGdUKm0VppL2KPJ9e-R0NreBESo_g@mail.gmail.com> (raw)
Regressions found on all devices LTP containers test cases failed on
Linux next-20220420. [1]
- ltp-containers-tests/netns_comm_ns_exec_ipv6_ioctl
- ltp-containers-tests/netns_breakns_ns_exec_ipv6_netlink
- ltp-containers-tests/netns_breakns_ip_ipv6_netlink
- ltp-containers-tests/netns_breakns_ns_exec_ipv4_ioctl
- ltp-containers-tests/netns_breakns_ip_ipv4_netlink
- ltp-containers-tests/netns_comm_ip_ipv6_ioctl
- ltp-containers-tests/netns_comm_ip_ipv4_netlink
- ltp-containers-tests/netns_comm_ns_exec_ipv4_netlink
- ltp-containers-tests/netns_breakns_ns_exec_ipv6_ioctl
- ltp-containers-tests/netns_comm_ip_ipv6_netlink
- ltp-containers-tests/netns_comm_ns_exec_ipv4_ioctl
- ltp-containers-tests/netns_breakns_ns_exec_ipv4_netlink
- ltp-containers-tests/netns_breakns_ip_ipv4_ioctl
- ltp-containers-tests/netns_comm_ip_ipv4_ioctl
- ltp-containers-tests/netns_breakns_ip_ipv6_ioctl
- ltp-containers-tests/netns_comm_ns_exec_ipv6_netlink
Test log:
---------
netns_breakns 1 TINFO: timeout per run is 0h 15m 0s
Command \"add\" is unknown, try \"ip link help\".
netns_breakns 1 TBROK: unable to create veth pair devices
Command \"delete\" is unknown, try \"ip link help\".
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
metadata:
git_ref: master
git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git_sha: f1244c81da13009dbf61cb807f45881501c44789
git_describe: next-20220420
kernel_version: 5.18.0-rc3
kernel-config: https://builds.tuxbuild.com/283Ot2o4P4hh7rNSH56BnbPbNba/config
build-url: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next/-/pipelines/520334286
artifact-location: https://builds.tuxbuild.com/283Ot2o4P4hh7rNSH56BnbPbNba
I will bisect these failures.
--
Linaro LKFT
https://lkft.linaro.org
[1] https://lkft.validation.linaro.org/scheduler/job/4925635#L1272
next reply other threads:[~2022-04-21 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 12:42 Naresh Kamboju [this message]
2022-04-21 12:46 ` [next] LTP: netns_breakns: Command \"add\" is unknown, try \"ip link help\" Ido Schimmel
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+G9fYvO5OERA0k-r=Q8gbGdUKm0VppL2KPJ9e-R0NreBESo_g@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=Raju.Lakkaraju@microchip.com \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=vadimp@nvidia.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).