❌ FAIL: Test report for kernel 5.11.0-rc7 (mainline.kernel.org-clang)

[CKI Project]

Hello,

We ran automated tests on a recent commit from this kernel tree:

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Commit: 92bf22614b21 - Linux 5.11-rc7

The results of these automated tests are provided below.

Overall result: FAILED (see details below)
Merge: OK
Compile: OK
Selftests compile: FAILED
Tests: FAILED

All kernel binaries, config files, and logs are available for download here:

https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/02/07/623301

One or more kernel tests failed:

ppc64le:
❌ Networking bridge: sanity
❌ Networking route: pmtu
❌ Networking route_func - local
❌ Networking route_func - forward
❌ Networking tunnel: geneve basic test
❌ Networking tunnel: gre basic
❌ L2TP basic test
❌ Networking tunnel: vxlan basic
❌ Networking ipsec: basic netns - tunnel

aarch64:
❌ LTP
❌ Networking bridge: sanity
❌ Networking route: pmtu
❌ Networking route_func - local
❌ Networking route_func - forward
❌ Networking tunnel: geneve basic test
❌ Networking tunnel: gre basic
❌ L2TP basic test
❌ Networking tunnel: vxlan basic
❌ Networking ipsec: basic netns - transport
❌ Networking ipsec: basic netns - tunnel

x86_64:
❌ LTP

We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.

Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.

,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________

Compile testing
---------------

We compiled the kernel for 3 architectures:

aarch64:
make options: make LLVM=1 -j24 INSTALL_MOD_STRIP=1 targz-pkg

ppc64le:
make options: make CC=clang -j24 INSTALL_MOD_STRIP=1 targz-pkg

x86_64:
make options: make LLVM=1 -j24 INSTALL_MOD_STRIP=1 targz-pkg


We built the following selftests:

x86_64:
net: fail
bpf: fail
install and packaging: fail

You can find the full log (build-selftests.log) in the artifact storage above.


Hardware testing
----------------
We booted each kernel and ran the following tests:

aarch64:
Host 1:
⏱ Boot test
⏱ storage: software RAID testing
⏱ xfstests - ext4
⏱ xfstests - xfs
⏱ xfstests - btrfs
⏱ IPMI driver test
⏱ IPMItool loop stress test
⏱ selinux-policy: serge-testsuite
⏱ Storage blktests
⏱ Storage block - filesystem fio test
⏱ Storage block - queue scheduler test
⏱ Storage nvme - tcp
⏱ Storage: swraid mdadm raid_module test
⏱ stress: stress-ng

Host 2:

⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.

✅ Boot test
✅ ACPI table test
✅ ACPI enabled test
❌ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
❌ Networking bridge: sanity
✅ Networking socket: fuzz
✅ Networking: igmp conformance test
❌ Networking route: pmtu
❌ Networking route_func - local
❌ Networking route_func - forward
✅ Networking TCP: keepalive test
✅ Networking UDP: socket
❌ Networking tunnel: geneve basic test
❌ Networking tunnel: gre basic
❌ L2TP basic test
❌ Networking tunnel: vxlan basic
❌ Networking ipsec: basic netns - transport
❌ Networking ipsec: basic netns - tunnel
✅ Libkcapi AF_ALG test
✅ pciutils: update pci ids test
✅ ALSA PCM loopback test
✅ ALSA Control (mixer) Userspace Element test
✅ storage: SCSI VPD
🚧 ✅ CIFS Connectathon
🚧 ✅ POSIX pjd-fstest suites
🚧 ⚡⚡⚡ Firmware test suite
🚧 ✅ jvm - jcstress tests
🚧 ✅ Memory function: kaslr
🚧 ✅ Ethernet drivers sanity
🚧 ✅ Networking firewall: basic netfilter test
🚧 ✅ audit: audit testsuite test
🚧 ✅ trace: ftrace/tracer
🚧 ✅ kdump - kexec_boot

ppc64le:
Host 1:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
❌ Networking bridge: sanity
✅ Networking socket: fuzz
❌ Networking route: pmtu
❌ Networking route_func - local
❌ Networking route_func - forward
✅ Networking TCP: keepalive test
✅ Networking UDP: socket
❌ Networking tunnel: geneve basic test
❌ Networking tunnel: gre basic
❌ L2TP basic test
❌ Networking tunnel: vxlan basic
❌ Networking ipsec: basic netns - tunnel
✅ Libkcapi AF_ALG test
✅ pciutils: update pci ids test
✅ ALSA PCM loopback test
✅ ALSA Control (mixer) Userspace Element test
🚧 ✅ CIFS Connectathon
🚧 ✅ POSIX pjd-fstest suites
🚧 ✅ jvm - jcstress tests
🚧 ✅ Memory function: kaslr
🚧 ✅ Ethernet drivers sanity
🚧 ✅ Networking firewall: basic netfilter test
🚧 ✅ audit: audit testsuite test
🚧 ✅ trace: ftrace/tracer

x86_64:
Host 1:

⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.

✅ Boot test
✅ storage: software RAID testing
🚧 ❌ CPU: Frequency Driver Test
🚧 ✅ CPU: Idle Test
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ xfstests - nfsv4.2
🚧 ✅ xfstests - cifsv3.11
🚧 ❌ IPMI driver test
🚧 ✅ IPMItool loop stress test
🚧 ❌ selinux-policy: serge-testsuite
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ❌ Storage nvme - tcp
🚧 ⚡⚡⚡ Storage nvdimm ndctl test suite
🚧 ✅ Storage: swraid mdadm raid_module test
🚧 ✅ stress: stress-ng

Host 2:
✅ Boot test
🚧 ✅ kdump - sysrq-c
🚧 ✅ kdump - file-load

Host 3:

⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.

✅ Boot test
✅ ACPI table test
❌ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Networking bridge: sanity
✅ Networking socket: fuzz
✅ Networking: igmp conformance test
✅ Networking route: pmtu
✅ Networking route_func - local
✅ Networking route_func - forward
✅ Networking TCP: keepalive test
✅ Networking UDP: socket
✅ Networking tunnel: geneve basic test
✅ Networking tunnel: gre basic
✅ L2TP basic test
✅ Networking tunnel: vxlan basic
✅ Networking ipsec: basic netns - transport
✅ Networking ipsec: basic netns - tunnel
✅ Libkcapi AF_ALG test
✅ pciutils: sanity smoke test
✅ pciutils: update pci ids test
✅ ALSA PCM loopback test
✅ ALSA Control (mixer) Userspace Element test
✅ storage: SCSI VPD
🚧 ✅ CIFS Connectathon
🚧 ✅ POSIX pjd-fstest suites
🚧 ⚡⚡⚡ Firmware test suite
🚧 ✅ jvm - jcstress tests
🚧 ✅ Memory function: kaslr
🚧 ✅ Ethernet drivers sanity
🚧 ✅ Networking firewall: basic netfilter test
🚧 ✅ audit: audit testsuite test
🚧 ✅ trace: ftrace/tracer
🚧 ✅ kdump - kexec_boot

Test sources: https://gitlab.com/cki-project/kernel-tests
💚 Pull requests are welcome for new tests or improvements to existing tests!

Aborted tests
-------------
Tests that didn't complete running successfully are marked with ⚡⚡⚡.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.

Waived tests
------------
If the test run included waived tests, they are marked with 🚧. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.

Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with ⏱.

[CKI Project]

Hello,

We ran automated tests on a recent commit from this kernel tree:

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

Commit: e0756cfc7d7c - Merge tag 'trace-v5.11-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace

The results of these automated tests are provided below.

Overall result: FAILED (see details below)
Merge: OK
Compile: OK
Selftests compile: FAILED
Tests: FAILED

All kernel binaries, config files, and logs are available for download here:

https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/02/08/623350

One or more kernel tests failed:

aarch64:
❌ LTP

x86_64:
❌ LTP

We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.

Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.

,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________

Compile testing
---------------

We compiled the kernel for 3 architectures:

aarch64:

make options: make LLVM=1 -j30 INSTALL_MOD_STRIP=1 targz-pkg

ppc64le:
make options: make CC=clang -j30 INSTALL_MOD_STRIP=1 targz-pkg

x86_64:
make options: make LLVM=1 -j30 INSTALL_MOD_STRIP=1 targz-pkg

We built the following selftests:

x86_64:
net: fail
bpf: fail
install and packaging: fail

You can find the full log (build-selftests.log) in the artifact storage above.


Hardware testing
----------------
We booted each kernel and ran the following tests:

aarch64:
Host 1:

Host 2:

⏱ Boot test
⏱ storage: software RAID testing
⏱ xfstests - ext4
⏱ xfstests - xfs
⏱ xfstests - btrfs
⏱ IPMI driver test
⏱ IPMItool loop stress test
⏱ selinux-policy: serge-testsuite
⏱ Storage blktests
⏱ Storage block - filesystem fio test
⏱ Storage block - queue scheduler test
⏱ Storage nvme - tcp
⏱ Storage: swraid mdadm raid_module test
⏱ stress: stress-ng

✅ storage: software RAID testing
🚧 ❌ CPU: Frequency Driver Test
🚧 ✅ CPU: Idle Test
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ xfstests - nfsv4.2
🚧 ✅ xfstests - cifsv3.11
🚧 ❌ IPMI driver test
🚧 ✅ IPMItool loop stress test
🚧 ❌ selinux-policy: serge-testsuite
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ Storage nvme - tcp
🚧 ⚡⚡⚡ Storage nvdimm ndctl test suite
🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ stress: stress-ng

[CKI Project]

Hello,

We ran automated tests on a recent commit from this kernel tree:

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

Commit: 291009f656e8 - Merge tag 'pm-5.11-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm

The results of these automated tests are provided below.

Overall result: FAILED (see details below)
Merge: OK
Compile: OK
Selftests compile: FAILED
Tests: FAILED

All kernel binaries, config files, and logs are available for download here:

https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/02/10/623699

net: OK
bpf: fail
install and packaging: OK

You can find the full log (build-selftests.log) in the artifact storage above.


Hardware testing
----------------
We booted each kernel and ran the following tests:

aarch64:
Host 1:

⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.

✅ Boot test

✅ storage: software RAID testing

🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ IPMI driver test
🚧 ✅ IPMItool loop stress test
🚧 ❌ selinux-policy: serge-testsuite
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ Storage nvme - tcp
🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ stress: stress-ng

Host 2:

ppc64le:

Host 1:

⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.

⚡⚡⚡ Boot test

⚡⚡⚡ LTP

Host 2:

⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.

⚡⚡⚡ Boot test

⚡⚡⚡ LTP

Host 3:
⏱ Boot test

⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.

✅ Boot test
✅ storage: software RAID testing
🚧 ❌ CPU: Frequency Driver Test
🚧 ✅ CPU: Idle Test
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ xfstests - nfsv4.2
🚧 ✅ xfstests - cifsv3.11
🚧 ✅ IPMI driver test
🚧 ✅ IPMItool loop stress test
🚧 ❌ selinux-policy: serge-testsuite
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ❌ Storage nvme - tcp
🚧 ⚡⚡⚡ Storage nvdimm ndctl test suite
🚧 ✅ Storage: swraid mdadm raid_module test
🚧 ✅ stress: stress-ng

Host 3:

✅ Boot test
🚧 ✅ kdump - sysrq-c
🚧 ✅ kdump - file-load

[Nathan Chancellor]

On Thu, Feb 11, 2021 at 05:11:07PM -0000, CKI Project wrote:
>
> Hello,
>
> We ran automated tests on a recent commit from this kernel tree:
>
> Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> Commit: 291009f656e8 - Merge tag 'pm-5.11-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
>
> The results of these automated tests are provided below.
>
> Overall result: FAILED (see details below)
> Merge: OK
> Compile: OK
> Selftests compile: FAILED
> Tests: FAILED
>
> All kernel binaries, config files, and logs are available for download here:
>
> https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/02/10/623699
>
> One or more kernel tests failed:
>
> aarch64:
> ❌ LTP
>
> x86_64:
> ❌ LTP
>

It seems like we are very close to getting a passing result... From what
I can tell, the failing tests are logged in these two files:

9548629_aarch64_1_commands.fail.log
9548632_x86_64_1_commands.fail.log

which shows only one test failing: ld01.sh

which appears to be this one:

https://github.com/linux-test-project/ltp/blob/c5004bf071bf8ca96a01f03bde873e9292f7f83b/testcases/commands/ld/ld01.sh

I do not understand how cc.out could have ld in it, when CC is clearly
gcc from the log... it passes in my testing. Has the test been modified
on your end?

Cheers,
Nathan

[Rachel Sibley]

We haven't updated recently, we just wrap around the upstream test suite and I don't see any recent change to the ld01 test ?
I also see it fail the same way on the gcc mainline kernels:

https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/02/10/623698/build_x86_64_redhat%3A1101938/tests/LTP/9548639_x86_64_1_commands.fail.log
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/02/10/623698/build_aarch64_redhat%3A1101939/tests/LTP/9548637_aarch64_1_commands.fail.log

Jan do you know anything about this failure ?

>>> 2:ld01_sh FAIL <<<
###############################################################################
# Test Num : 2 #
# Test Case : ld01_sh #
# Test Result : FAIL #
###############################################################################

1 <<<test_start>>>
2 tag=ld01_sh stime=1613000729
3 cmdline="ld01.sh"
4 contacts=""
5 analysis=exit
6 <<<test_output>>>
7 ld01 1 TINFO: timeout per run is 0h 5m 0s
8 ld01 1 TPASS: ld x.o y.o 2> ld.out failed as expected
9 ld01 1 TPASS: Missing files were reported
10 ld01 2 TPASS: gcc x.o y.o 2> cc.out failed as expected
11 ld01 2 TFAIL: Missing files were not reported
12 /usr/bin/ld: cannot find x.o: No such file or directory
13 /usr/bin/ld: cannot find y.o: No such file or directory
14 collect2: error: ld returned 1 exit status
15 ld01 3 TPASS: ld -shared f1.o d1.o -o test.so passed as expected
16 ld01 3 TPASS: Shared library could be build
17 ld01 4 TPASS: ld -Bdynamic -shared f1.o d1.o -o test.so passed as expected
18 ld01 4 TPASS: ld -Bstatic -L. main.o rd1.o test.so -o a.out failed as expected
19 ld01 5 TPASS: ld -Bdynamic -shared main.o f1.o rf1.o -o test.so -L/usr/lib/ passed as expected
20 ld01 5 TPASS: ld -Bstatic -r main.o f1.o rf1.o test.so -L/usr/lib/ 2> ld.out failed as expected
21 ld: attempted static link of dynamic object `test.so'
22 ld01 5 TPASS: Got expected error message

Nathan, btw we just started cc'ing you on regular mainline reports built with gcc, but please let us know if it's too much
spam and we can turn it off.

>
> Cheers,
> Nathan
>
>

[Jan Stancek]

I haven't seen this before and don't see it localy. Is it specific to Fedora Rawhide?

[Rachel Sibley]

Yes it looks like it's specific to rawhide, at least I can't reproduce it on Fedora 33 with the same kernel.

>