linux-kernel - Re: [linus:master] [selftests/tc] d227cc0b1e: kernel-selftests.tc-testing.tdc.sh.fail

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 16 Nov 2023 11:16:33 -0300
From:   Pedro Tammela <pctammela@...atatu.com>
To:     kernel test robot <oliver.sang@...el.com>
Cc:     oe-lkp@...ts.linux.dev, lkp@...el.com,
        linux-kernel@...r.kernel.org, Paolo Abeni <pabeni@...hat.com>,
        Davide Caratti <dcaratti@...hat.com>,
        Jamal Hadi Salim <jhs@...atatu.com>, netdev@...r.kernel.org
Subject: Re: [linus:master] [selftests/tc] d227cc0b1e:
 kernel-selftests.tc-testing.tdc.sh.fail

On 16/11/2023 03:42, kernel test robot wrote:
> 
> 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@...el.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
> 
> 
> 

Hi!
Thanks for the report.
I'm trying to address this issue and others in this series:
[PATCH net-next 0/4] selftests: tc-testing: updates to tdc

I have seen this timeout in other CIs as well, but I cannot reproduce 
locally, even with the CI build running on my laptop. I did notice in my 
local tests that KVM is a big factor for test completion, so it begs the 
question, is it running on a KVM enabled instance?

If there's any document describing the runner instances I would be 
interested too.