From: kernel test robot <oliver.sang@intel.com>
To: Puranjay Mohan <puranjay12@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Alexei Starovoitov <ast@kernel.org>, <bpf@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linux-next:master] [bpf/tests] daabb2b098: kernel-selftests.net.test_bpf.sh.fail
Date: Wed, 11 Oct 2023 21:20:17 +0800 [thread overview]
Message-ID: <202310111838.46ff5b6a-oliver.sang@intel.com> (raw)
hi, Puranjay Mohan,
we reported same issue when this commit is a review patch as:
https://lore.kernel.org/all/202309261451.8934f9ad-oliver.sang@intel.com/
now we noticed this commit is in linux-next/master and we still observed
failure.
is there any requirements to run new tests? Thanks
Hello,
kernel test robot noticed "kernel-selftests.net.test_bpf.sh.fail" on:
commit: daabb2b098e04753fa3d1b1feed13e5a61bef61c ("bpf/tests: add tests for cpuv4 instructions")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 719136e5c24768ebdf80b9daa53facebbdd377c3]
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/202310111838.46ff5b6a-oliver.sang@intel.com
....
# timeout set to 1500
# selftests: net: test_bpf.sh
# test_bpf: [FAIL]
not ok 13 selftests: net: test_bpf.sh # exit=1
....
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231011/202310111838.46ff5b6a-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-10-11 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 13:20 kernel test robot [this message]
2023-10-11 14:01 ` Puranjay Mohan
2023-10-11 14:29 ` Puranjay Mohan
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=202310111838.46ff5b6a-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=puranjay12@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