From: kernel test robot <oliver.sang@intel.com>
To: Daniel Mendes <dmendes@redhat.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
"David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linux-next:master] [kselftest] 9c2a19f715: kernel-selftests.net.rtnetlink.sh.gretap.fail
Date: Wed, 11 Oct 2023 21:50:46 +0800 [thread overview]
Message-ID: <202310112125.c5889283-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "kernel-selftests.net.rtnetlink.sh.gretap.fail" on:
commit: 9c2a19f71515553a874e2bf31655ac2264a66e37 ("kselftest: rtnetlink.sh: add verbose flag")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 18030226a48de1fbfabf4ae16aaa2695a484254f]
in testcase: kernel-selftests
version: kernel-selftests-x86_64-60acb023-1_20230329
with following parameters:
group: net
compiler: gcc-12
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz (Cascade Lake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202310112125.c5889283-oliver.sang@intel.com
# timeout set to 1500
# selftests: net: rtnetlink.sh
# PASS: policy routing
# PASS: route get
# PASS: preferred_lft addresses have expired
# PASS: promote_secondaries complete
# PASS: tc htb hierarchy
# PASS: gre tunnel endpoint
# FAIL: gretap <----------
# PASS: ip6gretap
# PASS: erspan
# PASS: ip6erspan
# PASS: bridge setup
# PASS: ipv6 addrlabel
# PASS: set ifalias f007c594-8cc4-4bfa-bf82-fef2dfb81ad2 for test-dummy0
# PASS: vrf
# PASS: macsec
# PASS: macsec_offload
# PASS: ipsec
# PASS: ipsec_offload
# PASS: bridge fdb get
# PASS: neigh get
# PASS: bridge_parent_id
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# Error: ipv4: Address not found.
# Error: ipv4: Address not found.
# FAIL: address proto IPv4
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# Error: ipv6: address not found.
# Error: ipv6: address not found.
# FAIL: address proto IPv6
not ok 15 selftests: net: rtnetlink.sh # exit=1
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231011/202310112125.c5889283-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-11 13:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202310112125.c5889283-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=davem@davemloft.net \
--cc=dmendes@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
/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