From: kernel test robot <oliver.sang@intel.com>
To: Eric Dumazet <edumazet@google.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
"Linux Memory Management List" <linux-mm@kvack.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Dave Taht" <dave.taht@gmail.com>,
"Willem de Bruijn" <willemb@google.com>,
"Soheil Hassas Yeganeh" <soheil@google.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
netdev@vger.kernel.org, aubrey.li@linux.intel.com,
yu.c.chen@intel.com, oliver.sang@intel.com
Subject: [linux-next:master] [net_sched] 29f834aa32: kernel-selftests.net.so_txtime.sh.fail
Date: Fri, 20 Oct 2023 15:17:41 +0800 [thread overview]
Message-ID: <202310201422.a22b0999-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "kernel-selftests.net.so_txtime.sh.fail" on:
commit: 29f834aa326e659ed354c406056e94ea3d29706a ("net_sched: sch_fq: add 3 bands and WRR scheduling")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master e3b18f7200f45d66f7141136c25554ac1e82009b]
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/202310201422.a22b0999-oliver.sang@intel.com
besides, we also noticed kernel-selftests.net.cmsg_time.sh.fail which does not
happen on parent.
5579ee462dfe7682 29f834aa326e659ed354c406056
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:6 100% 6:6 kernel-selftests.net.cmsg_time.sh.fail
:6 100% 6:6 kernel-selftests.net.so_txtime.sh.fail
# timeout set to 1500
# selftests: net: so_txtime.sh
#
# SO_TXTIME ipv4 clock monotonic
# payload:a delay:296 expected:0 (us)
#
# SO_TXTIME ipv6 clock monotonic
# payload:a delay:279 expected:0 (us)
#
# SO_TXTIME ipv6 clock monotonic
# ./so_txtime: recv: timeout: Resource temporarily unavailable
not ok 30 selftests: net: so_txtime.sh # exit=1
....
# timeout set to 1500
# selftests: net: cmsg_time.sh
# Case UDPv4 - TXTIME abs returned '', expected 'OK'
# FAIL - 1/36 cases failed
not ok 59 selftests: net: cmsg_time.sh # exit=1
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231020/202310201422.a22b0999-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-10-20 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 7:17 kernel test robot [this message]
2023-10-20 19:52 ` [linux-next:master] [net_sched] 29f834aa32: kernel-selftests.net.so_txtime.sh.fail Eric Dumazet
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=202310201422.a22b0999-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=dave.taht@gmail.com \
--cc=edumazet@google.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=soheil@google.com \
--cc=toke@redhat.com \
--cc=willemb@google.com \
--cc=yu.c.chen@intel.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