From: kernel test robot <oliver.sang@intel.com>
To: Pedro Tammela <pctammela@mojatatu.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Davide Caratti <dcaratti@redhat.com>,
"Jamal Hadi Salim" <jhs@mojatatu.com>, <netdev@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linus:master] [selftests/tc] d227cc0b1e: kernel-selftests.tc-testing.tdc.sh.fail
Date: Thu, 16 Nov 2023 14:42:59 +0800 [thread overview]
Message-ID: <202311161129.3b45ed53-oliver.sang@intel.com> (raw)
hi, Pedro Tammela,
we reported
"[linux-next:master] [selftests/tc] d227cc0b1e: kernel-selftests.tc-testing.tdc.sh.fail"
in
https://lore.kernel.org/all/202310251624.5ce67bed-oliver.sang@intel.com/
when this commit is in linux-next/master
now we noticed this commit is in mainline, and we observed same issue.
we noticed test can pass upon parent commit, looks like:
# timeout set to 900
# selftests: tc-testing: tdc.sh
# considering category actions
# -- scapy/SubPlugin.__init__
# -- buildebpf/SubPlugin.__init__
# -- ns/SubPlugin.__init__
# Setting up namespaces and devices...
# Test d959: Add cBPF action with valid bytecode
# Test f84a: Add cBPF action with invalid bytecode
...
#
ok 1 selftests: tc-testing: tdc.sh
but after this commit, seems test cannot start as below details.
want to consult if there is any prerequisite to run
kernel-selftests.tc-testing.tdc.sh
after this commit?
Hello,
kernel test robot noticed "kernel-selftests.tc-testing.tdc.sh.fail" on:
commit: d227cc0b1ee12560f7489239fc69ba6a10b14607 ("selftests/tc-testing: update test definitions for local resources")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linux-next/master 8728c14129df7a6e29188a2e737b4774fb200953]
in testcase: kernel-selftests
version: kernel-selftests-x86_64-60acb023-1_20230329
with following parameters:
group: tc-testing
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/202311161129.3b45ed53-oliver.sang@intel.com
KERNEL SELFTESTS: linux_headers_dir is /usr/src/linux-headers-x86_64-rhel-8.3-kselftests-d227cc0b1ee12560f7489239fc69ba6a10b14607
2023-11-15 20:15:35 ln -sf /usr/sbin/iptables-nft /usr/bin/iptables
2023-11-15 20:15:35 ln -sf /usr/sbin/ip6tables-nft /usr/bin/ip6tables
2023-11-15 20:15:35 sed -i s/default_timeout=45/default_timeout=300/ kselftest/runner.sh
LKP WARN miss config CONFIG_ATM= of tc-testing/config
LKP WARN miss config CONFIG_PTP_1588_CLOCK_MOCK= of tc-testing/config
2023-11-15 20:15:39 make -j36 -C tc-testing
make: Entering directory '/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-d227cc0b1ee12560f7489239fc69ba6a10b14607/tools/testing/selftests/tc-testing'
clang -I. -I/include/uapi -idirafter /opt/cross/clang-4a5ac14ee9/lib/clang/17/include -idirafter /usr/local/include -idirafter /usr/lib/gcc/x86_64-linux-gnu/12/../../../../x86_64-linux-gnu/include -idirafter /usr/include/x86_64-linux-gnu -idirafter /usr/include -Wno-compare-distinct-pointer-types \
-O2 --target=bpf -emit-llvm -c action.c -o - | \
llc -march=bpf -mcpu=probe -filetype=obj -o /usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-d227cc0b1ee12560f7489239fc69ba6a10b14607/tools/testing/selftests/tc-testing/action.o
make: Leaving directory '/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-d227cc0b1ee12560f7489239fc69ba6a10b14607/tools/testing/selftests/tc-testing'
2023-11-15 20:15:44 make quicktest=1 run_tests -C tc-testing
make: Entering directory '/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-d227cc0b1ee12560f7489239fc69ba6a10b14607/tools/testing/selftests/tc-testing'
TAP version 13
1..1
# timeout set to 900
# selftests: tc-testing: tdc.sh
#
not ok 1 selftests: tc-testing: tdc.sh # TIMEOUT 900 seconds
make: Leaving directory '/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-d227cc0b1ee12560f7489239fc69ba6a10b14607/tools/testing/selftests/tc-testing'
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231116/202311161129.3b45ed53-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-11-16 6:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 6:42 kernel test robot [this message]
2023-11-16 14:16 ` Pedro Tammela
2023-11-17 1:27 ` Pedro Tammela
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=202311161129.3b45ed53-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=dcaratti@redhat.com \
--cc=jhs@mojatatu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.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
all inboxes | Powered by JetHome®