netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Sriram Yagnaraman <sriram.yagnaraman@est.tech>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
	<oliver.sang@intel.com>
Subject: [linus:master] [selftests]  8ae9efb859: kernel-selftests.net.fib_tests.sh.fail
Date: Tue, 19 Sep 2023 16:32:09 +0800	[thread overview]
Message-ID: <202309191658.c00d8b8-oliver.sang@intel.com> (raw)


hi, Sriram Yagnaraman,

we noticed two new added tests failed in our test environment.
want to consult with you what's the dependency and requirement to run them?
Thanks a lot!

Hello,

kernel test robot noticed "kernel-selftests.net.fib_tests.sh.fail" on:

commit: 8ae9efb859c05a54ac92b3336c6ca0597c9c8cdb ("selftests: fib_tests: Add multipath list receive tests")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

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/202309191658.c00d8b8-oliver.sang@intel.com



# timeout set to 1500
# selftests: net: fib_tests.sh
# 
# Single path route test
#     Start point
#     TEST: IPv4 fibmatch                                                 [ OK ]
#     TEST: IPv6 fibmatch                                                 [ OK ]
#     Nexthop device deleted
#     TEST: IPv4 fibmatch - no route                                      [ OK ]
#     TEST: IPv6 fibmatch - no route                                      [ OK ]

...

# 
# Fib6 garbage collection test
#     TEST: ipv6 route garbage collection                                 [ OK ]
# 
# IPv4 multipath list receive tests
#     TEST: Multipath route hit ratio (.06)                               [FAIL]
# 
# IPv6 multipath list receive tests
#     TEST: Multipath route hit ratio (.10)                               [FAIL]
# 
# Tests passed: 223
# Tests failed:   2
not ok 17 selftests: net: fib_tests.sh # exit=1



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230919/202309191658.c00d8b8-oliver.sang@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


             reply	other threads:[~2023-09-19  8:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19  8:32 kernel test robot [this message]
2023-09-25 18:18 ` [linus:master] [selftests] 8ae9efb859: kernel-selftests.net.fib_tests.sh.fail Sriram Yagnaraman
2023-10-01 14:50   ` Ido Schimmel
2023-10-07  7:23     ` Oliver Sang

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=202309191658.c00d8b8-oliver.sang@intel.com \
    --to=oliver.sang@intel.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=oe-lkp@lists.linux.dev \
    --cc=sriram.yagnaraman@est.tech \
    /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).