From: kernel test robot <oliver.sang@intel.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Alan Maguire <alan.maguire@oracle.com>,
Nicolas Schier <n.schier@avm.de>, Miguel Ojeda <ojeda@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
"Martin Rodriguez Reboredo" <yakoyoku@gmail.com>,
<linux-kbuild@vger.kernel.org>, <bpf@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linus:master] [kbuild] 72d091846d: kernel-selftests.net.udpgro_bench.sh.fail
Date: Wed, 22 Nov 2023 16:22:53 +0800 [thread overview]
Message-ID: <202311221453.9e6d5ac0-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "kernel-selftests.net.udpgro_bench.sh.fail" on:
commit: 72d091846de935e0942a8a0f1fe24ff739d85d76 ("kbuild: avoid too many execution of scripts/pahole-flags.sh")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 7475e51b87969e01a6812eac713a1c8310372e8a]
[test failed on linux-next/master eff99d8edbed7918317331ebd1e365d8e955d65e]
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/202311221453.9e6d5ac0-oliver.sang@intel.com
besides kernel-selftests.net.udpgro_bench.sh, we also observed below tests
failed upon this commit but can pass on parent.
7f6d8f7e43fb516f 72d091846de935e0942a8a0f1fe
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:20 100% 20:20 kernel-selftests.net.udpgro.sh.fail
:20 100% 20:20 kernel-selftests.net.udpgro_bench.sh.fail
:20 100% 20:20 kernel-selftests.net.udpgro_frglist.sh.fail
:20 100% 20:20 kernel-selftests.net.veth.sh.fail
....
# timeout set to 1500
# selftests: net: udpgro_bench.sh
# Missing ../bpf/xdp_dummy.bpf.o. Build bpf selftest first
not ok 25 selftests: net: udpgro_bench.sh # exit=255
# timeout set to 1500
# selftests: net: udpgro.sh
# Missing ../bpf/xdp_dummy.bpf.o. Build bpf selftest first
not ok 26 selftests: net: udpgro.sh # exit=255
....
# timeout set to 1500
# selftests: net: udpgro_frglist.sh
# Missing ../bpf/xdp_dummy.bpf.o. Build bpf selftest first
not ok 53 selftests: net: udpgro_frglist.sh # exit=255
# timeout set to 1500
# selftests: net: veth.sh
# Missing ../bpf/xdp_dummy.bpf.o. Build bpf selftest first
not ok 54 selftests: net: veth.sh # exit=1
....
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231122/202311221453.9e6d5ac0-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-22 8:23 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=202311221453.9e6d5ac0-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=alan.maguire@oracle.com \
--cc=bpf@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--cc=n.schier@avm.de \
--cc=oe-lkp@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=yakoyoku@gmail.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