Check out this report and any autotriaged failures in our web dashboard: https://datawarehouse.cki-project.org/kcidb/checkouts/38921
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Commit: eabfed45bc7c - io_uring: drop the old style inflight file tracking
The results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: OK Tests: FAILED Targeted tests: NO
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix...
One or more kernel tests failed:
s390x: ❌ LTP - syscalls ❌ storage: dm/common
ppc64le: ❌ LTP - syscalls ❌ storage: dm/common ❌ lvm thinp sanity
x86_64: ❌ lvm thinp sanity 💥 lvm thinp stqe test ❌ LTP - syscalls ❌ storage: dm/common ❌ Reboot test
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 4 architectures:
aarch64: make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg
ppc64le: make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg
s390x: make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg
x86_64: make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg
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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup ⚡⚡⚡ Boot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ IPMI driver test ⚡⚡⚡ IPMItool loop stress test ⚡⚡⚡ selinux-policy: serge-testsuite ⚡⚡⚡ Storage blktests - blk ⚡⚡⚡ Storage block - filesystem fio test ⚡⚡⚡ Storage block - queue scheduler test ⚡⚡⚡ lvm thinp sanity ⚡⚡⚡ storage: software RAID testing ⚡⚡⚡ Storage: swraid mdadm raid_module test ⚡⚡⚡ stress: stress-ng - interrupt ⚡⚡⚡ stress: stress-ng - cpu ⚡⚡⚡ stress: stress-ng - cpu-cache ⚡⚡⚡ stress: stress-ng - memory 🚧 ⚡⚡⚡ Podman system test - as root 🚧 ⚡⚡⚡ Podman system test - as user 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - storage fio numa 🚧 ⚡⚡⚡ lvm thinp stqe test 🚧 ⚡⚡⚡ lvm cache test 🚧 ⚡⚡⚡ stress: stress-ng - os ⚡⚡⚡ Reboot test
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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup ⚡⚡⚡ Boot test 🚧 ⚡⚡⚡ Storage blktests - nvmeof-mp ⚡⚡⚡ Reboot test
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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup ⚡⚡⚡ Boot test ⚡⚡⚡ ACPI table test ⚡⚡⚡ ACPI enabled test ⚡⚡⚡ LTP - cve ⚡⚡⚡ LTP - sched ⚡⚡⚡ LTP - syscalls ⚡⚡⚡ LTP - can ⚡⚡⚡ LTP - commands ⚡⚡⚡ LTP - containers ⚡⚡⚡ LTP - dio ⚡⚡⚡ LTP - fs ⚡⚡⚡ LTP - fsx ⚡⚡⚡ LTP - math ⚡⚡⚡ LTP - hugetlb ⚡⚡⚡ LTP - mm ⚡⚡⚡ LTP - nptl ⚡⚡⚡ LTP - pty ⚡⚡⚡ LTP - ipc ⚡⚡⚡ LTP - tracing ⚡⚡⚡ LTP: openposix test suite ⚡⚡⚡ CIFS Connectathon ⚡⚡⚡ POSIX pjd-fstest suites ⚡⚡⚡ NFS Connectathon ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ jvm - jcstress tests ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) ⚡⚡⚡ Networking bridge: sanity ⚡⚡⚡ Ethernet drivers sanity ⚡⚡⚡ Networking MACsec: sanity ⚡⚡⚡ Networking socket: fuzz ⚡⚡⚡ Networking sctp-auth: sockopts test ⚡⚡⚡ Networking: igmp conformance test ⚡⚡⚡ Networking route: pmtu ⚡⚡⚡ Networking route_func - local ⚡⚡⚡ Networking route_func - forward ⚡⚡⚡ Networking TCP: keepalive test ⚡⚡⚡ Networking UDP: socket ⚡⚡⚡ Networking cki netfilter test ⚡⚡⚡ 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 ⚡⚡⚡ Networking vnic: ipvlan/basic ⚡⚡⚡ Libkcapi AF_ALG test ⚡⚡⚡ pciutils: update pci ids test ⚡⚡⚡ ALSA PCM loopback test ⚡⚡⚡ ALSA Control (mixer) Userspace Element test ⚡⚡⚡ storage: dm/common ⚡⚡⚡ lvm snapper test ⚡⚡⚡ storage: SCSI VPD ⚡⚡⚡ trace: ftrace/tracer 🚧 ⚡⚡⚡ i2c: i2cdetect sanity 🚧 ⚡⚡⚡ Firmware test suite 🚧 ⚡⚡⚡ Memory function: kaslr 🚧 ⚡⚡⚡ Networking tunnel: permtest 🚧 ⚡⚡⚡ Networking VRF: sanity 🚧 ⚡⚡⚡ audit: audit testsuite test 🚧 ⚡⚡⚡ Usex - version 1.9-29 🚧 ⚡⚡⚡ Storage: block zstd compression test 🚧 ⚡⚡⚡ Storage: block zstd smoke test ⚡⚡⚡ Reboot test
Host 4:
⚡ 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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup ⚡⚡⚡ Boot test ⚡⚡⚡ Networking bridge: sanity - mlx5 ⚡⚡⚡ Ethernet drivers sanity - mlx5 ⚡⚡⚡ Reboot test
Host 5:
⚡ 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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup ⚡⚡⚡ Boot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ IPMI driver test ⚡⚡⚡ IPMItool loop stress test ⚡⚡⚡ selinux-policy: serge-testsuite ⚡⚡⚡ Storage blktests - blk ⚡⚡⚡ Storage block - filesystem fio test ⚡⚡⚡ Storage block - queue scheduler test ⚡⚡⚡ lvm thinp sanity ⚡⚡⚡ storage: software RAID testing ⚡⚡⚡ Storage: swraid mdadm raid_module test ⚡⚡⚡ stress: stress-ng - interrupt ⚡⚡⚡ stress: stress-ng - cpu ⚡⚡⚡ stress: stress-ng - cpu-cache ⚡⚡⚡ stress: stress-ng - memory 🚧 ⚡⚡⚡ Podman system test - as root 🚧 ⚡⚡⚡ Podman system test - as user 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - storage fio numa 🚧 ⚡⚡⚡ lvm thinp stqe test 🚧 ⚡⚡⚡ lvm cache test 🚧 ⚡⚡⚡ stress: stress-ng - os ⚡⚡⚡ Reboot test
Host 6:
⚡ 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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup ⚡⚡⚡ Boot test ⚡⚡⚡ Networking bridge: sanity - mlx5 ⚡⚡⚡ Ethernet drivers sanity - mlx5 ⚡⚡⚡ Reboot test
ppc64le: Host 1: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ POSIX pjd-fstest suites ✅ NFS Connectathon ✅ Loopdev Sanity ✅ jvm - jcstress tests ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Networking bridge: sanity ✅ Ethernet drivers sanity ✅ Networking MACsec: sanity ✅ Networking socket: fuzz ✅ Networking sctp-auth: sockopts test ✅ Networking route: pmtu ✅ Networking route_func - local ✅ Networking route_func - forward ✅ Networking TCP: keepalive test ✅ Networking UDP: socket ✅ Networking cki netfilter test ✅ Networking tunnel: geneve basic test ✅ Networking tunnel: gre basic ✅ L2TP basic test ✅ Networking tunnel: vxlan basic ✅ Networking ipsec: basic netns - tunnel ✅ Networking vnic: ipvlan/basic ✅ Libkcapi AF_ALG test ✅ pciutils: update pci ids test ✅ ALSA PCM loopback test ✅ ALSA Control (mixer) Userspace Element test ❌ storage: dm/common ✅ lvm snapper test ✅ trace: ftrace/tracer 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ Memory function: kaslr 🚧 ✅ Networking tunnel: permtest 🚧 ✅ Networking VRF: sanity 🚧 ✅ audit: audit testsuite test 🚧 ✅ Usex - version 1.9-29 🚧 ✅ Storage: block zstd compression test 🚧 ✅ Storage: block zstd smoke test ✅ Reboot test
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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup ⚡⚡⚡ Boot test 🚧 ⚡⚡⚡ Storage blktests - nvmeof-mp ⚡⚡⚡ Reboot test
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.
🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ IPMI driver test ✅ IPMItool loop stress test ✅ selinux-policy: serge-testsuite ✅ Storage blktests - blk ✅ Storage block - filesystem fio test ✅ Storage block - queue scheduler test ❌ lvm thinp sanity ✅ storage: software RAID testing ✅ Storage: swraid mdadm raid_module test 🚧 ✅ Podman system test - as root 🚧 ✅ Podman system test - as user 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - storage fio numa 🚧 ✅ lvm thinp stqe test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ✅ lvm cache test ✅ Reboot test
Host 4: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test 🚧 ✅ Storage blktests - nvmeof-mp ✅ Reboot test
s390x: Host 1: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ POSIX pjd-fstest suites ✅ NFS Connectathon ✅ Loopdev Sanity ✅ jvm - jcstress tests ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Networking bridge: sanity ✅ Ethernet drivers sanity ✅ Networking MACsec: sanity ✅ Networking sctp-auth: sockopts test ✅ Networking route: pmtu ✅ Networking route_func - local ✅ Networking route_func - forward ✅ Networking TCP: keepalive test ✅ Networking UDP: socket ✅ Networking cki netfilter test ✅ 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 ✅ Networking vnic: ipvlan/basic ✅ Libkcapi AF_ALG test ❌ storage: dm/common ✅ lvm snapper test ✅ trace: ftrace/tracer 🚧 ✅ Memory function: kaslr 🚧 ✅ Networking tunnel: permtest 🚧 ✅ Networking VRF: sanity 🚧 ✅ audit: audit testsuite test 🚧 ✅ Storage: block zstd compression test 🚧 ✅ Storage: block zstd smoke test ✅ Reboot test
Host 2: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test 🚧 ✅ Storage blktests - nvmeof-mp ✅ Reboot test
Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ selinux-policy: serge-testsuite ✅ Storage blktests - blk ✅ Storage: swraid mdadm raid_module test ✅ stress: stress-ng - interrupt ✅ stress: stress-ng - cpu ✅ stress: stress-ng - cpu-cache ✅ stress: stress-ng - memory 🚧 ✅ Podman system test - as root 🚧 ✅ Podman system test - as user 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ lvm thinp stqe test 🚧 ✅ lvm cache test 🚧 ✅ stress: stress-ng - os ✅ Reboot test
x86_64: Host 1: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test 🚧 ✅ Storage blktests - nvmeof-mp ✅ Reboot test
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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup ⚡⚡⚡ Boot test ⚡⚡⚡ ACPI table test ⚡⚡⚡ LTP - cve ⚡⚡⚡ LTP - sched ⚡⚡⚡ LTP - syscalls ⚡⚡⚡ LTP - can ⚡⚡⚡ LTP - commands ⚡⚡⚡ LTP - containers ⚡⚡⚡ LTP - dio ⚡⚡⚡ LTP - fs ⚡⚡⚡ LTP - fsx ⚡⚡⚡ LTP - math ⚡⚡⚡ LTP - hugetlb ⚡⚡⚡ LTP - mm ⚡⚡⚡ LTP - nptl ⚡⚡⚡ LTP - pty ⚡⚡⚡ LTP - ipc ⚡⚡⚡ LTP - tracing ⚡⚡⚡ LTP: openposix test suite ⚡⚡⚡ CIFS Connectathon ⚡⚡⚡ POSIX pjd-fstest suites ⚡⚡⚡ NFS Connectathon ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ jvm - jcstress tests ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) ⚡⚡⚡ Networking bridge: sanity ⚡⚡⚡ Ethernet drivers sanity ⚡⚡⚡ Networking MACsec: sanity ⚡⚡⚡ Networking socket: fuzz ⚡⚡⚡ Networking sctp-auth: sockopts test ⚡⚡⚡ Networking: igmp conformance test ⚡⚡⚡ Networking route: pmtu ⚡⚡⚡ Networking route_func - local ⚡⚡⚡ Networking route_func - forward ⚡⚡⚡ Networking TCP: keepalive test ⚡⚡⚡ Networking UDP: socket ⚡⚡⚡ Networking cki netfilter test ⚡⚡⚡ 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 ⚡⚡⚡ Networking vnic: ipvlan/basic ⚡⚡⚡ Libkcapi AF_ALG test ⚡⚡⚡ pciutils: sanity smoke test ⚡⚡⚡ pciutils: update pci ids test ⚡⚡⚡ ALSA PCM loopback test ⚡⚡⚡ ALSA Control (mixer) Userspace Element test ⚡⚡⚡ storage: dm/common ⚡⚡⚡ lvm snapper test ⚡⚡⚡ storage: SCSI VPD ⚡⚡⚡ trace: ftrace/tracer 🚧 ⚡⚡⚡ xarray-idr-radixtree-test 🚧 ⚡⚡⚡ i2c: i2cdetect sanity 🚧 ⚡⚡⚡ Firmware test suite 🚧 ⚡⚡⚡ Memory function: kaslr 🚧 ⚡⚡⚡ Networking tunnel: permtest 🚧 ⚡⚡⚡ Networking VRF: sanity 🚧 ⚡⚡⚡ audit: audit testsuite test 🚧 ⚡⚡⚡ Usex - version 1.9-29 🚧 ⚡⚡⚡ Storage: block zstd compression test 🚧 ⚡⚡⚡ Storage: block zstd smoke test ⚡⚡⚡ Reboot test
Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ CPU: Die Test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ xfstests - nfsv4.2 ✅ xfstests - cifsv3.11 ✅ IPMI driver test ✅ IPMItool loop stress test ✅ selinux-policy: serge-testsuite ✅ Storage blktests - blk ✅ Storage block - filesystem fio test ✅ Storage block - queue scheduler test ❌ lvm thinp sanity ✅ storage: software RAID testing ✅ Storage: swraid mdadm raid_module test ✅ stress: stress-ng - interrupt ✅ stress: stress-ng - cpu ✅ stress: stress-ng - cpu-cache ✅ stress: stress-ng - memory 🚧 ❌ Podman system test - as root 🚧 ❌ Podman system test - as user 🚧 ✅ xfstests - btrfs 🚧 ❌ Storage blktests - nvme-tcp 🚧 ❌ Storage block - storage fio numa 🚧 💥 lvm thinp stqe test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ lvm cache test 🚧 ⚡⚡⚡ stress: stress-ng - os ⚡⚡⚡ Reboot test
Host 4: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ ACPI table test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ POSIX pjd-fstest suites ✅ NFS Connectathon ✅ Loopdev Sanity ✅ jvm - jcstress tests ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Networking bridge: sanity ✅ Ethernet drivers sanity ✅ Networking MACsec: sanity ✅ Networking socket: fuzz ✅ Networking sctp-auth: sockopts test ✅ Networking: igmp conformance test ✅ Networking route: pmtu ✅ Networking route_func - local ✅ Networking route_func - forward ✅ Networking TCP: keepalive test ✅ Networking UDP: socket ✅ Networking cki netfilter test ✅ 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 ✅ Networking vnic: ipvlan/basic ✅ Libkcapi AF_ALG test ✅ pciutils: sanity smoke test ✅ pciutils: update pci ids test ✅ ALSA PCM loopback test ✅ ALSA Control (mixer) Userspace Element test ❌ storage: dm/common ✅ lvm snapper test ✅ storage: SCSI VPD ✅ trace: ftrace/tracer 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ i2c: i2cdetect sanity 🚧 ✅ Firmware test suite 🚧 ❌ Memory function: kaslr 🚧 ✅ Networking tunnel: permtest 🚧 ✅ Networking VRF: sanity 🚧 ✅ audit: audit testsuite test 🚧 ✅ Usex - version 1.9-29 🚧 ✅ Storage: block zstd compression test 🚧 ✅ Storage: block zstd smoke test ❌ Reboot test
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 ⏱. Targeted tests -------------- Test runs for patches always include a set of base tests, plus some tests chosen based on the file paths modified by the patch. The latter are called "targeted tests". If no targeted tests are run, that means no patch-specific tests are available. Please, consider contributing a targeted test for related patches to increase test coverage. See https://docs.engineering.redhat.com/x/_wEZB for more details.
On Wed, Apr 13, 2022 at 06:03:14AM -0000, CKI Project wrote:
Check out this report and any autotriaged failures in our web dashboard: https://datawarehouse.cki-project.org/kcidb/checkouts/38921
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Commit: eabfed45bc7c - io_uring: drop the old style inflight file tracking
It's alive!
The results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: OK Tests: FAILED Targeted tests: NO
But things are failing.
Is this the CKI tool's issue, or is it the patches in the stable queue's issue?
Given that CKI has been dead for so long, I'll guess it's a CKI issue unless you all say otherwise.
thanks,
greg k-h
On Wed, Apr 13, 2022 at 8:24 AM Greg KH gregkh@linuxfoundation.org wrote:
On Wed, Apr 13, 2022 at 06:03:14AM -0000, CKI Project wrote:
Check out this report and any autotriaged failures in our web dashboard: https://datawarehouse.cki-project.org/kcidb/checkouts/38921
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Commit: eabfed45bc7c - io_uring: drop the old style inflight file trackingIt's alive!
The results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: OK Tests: FAILED Targeted tests: NOBut things are failing.
Is this the CKI tool's issue, or is it the patches in the stable queue's issue?
Given that CKI has been dead for so long, I'll guess it's a CKI issue unless you all say otherwise.
Hi,
yes, we finally got the builds fixed and are able to run the testing, and immediately hit the following Fedora bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2074083
We're looking into what exactly went wrong, the initial suspect is that the bug caused aborted test runs which confused the reporting system. Sorry about that, and thank you for reaching out about the problem!
The listed failures are actual failures (both test and kernel bugs), but not specific to the stable tree. They were already reported to the relevant places. If you wish, you can look into the details in the provided DataWarehouse link.
We're working on transforming the email reports to include the known issue detection that is currently provided in the dashboard, it should be in place in the (hopefully) near future. That should also stabilize the emails.
Veronika
thanks,
greg k-h
On Wed, Apr 13, 2022 at 2:51 PM Veronika Kabatova vkabatov@redhat.com wrote:
On Wed, Apr 13, 2022 at 8:24 AM Greg KH gregkh@linuxfoundation.org wrote:
On Wed, Apr 13, 2022 at 06:03:14AM -0000, CKI Project wrote:
Check out this report and any autotriaged failures in our web dashboard: https://datawarehouse.cki-project.org/kcidb/checkouts/38921
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Commit: eabfed45bc7c - io_uring: drop the old style inflight file trackingIt's alive!
The results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: OK Tests: FAILED Targeted tests: NOBut things are failing.
Is this the CKI tool's issue, or is it the patches in the stable queue's issue?
Given that CKI has been dead for so long, I'll guess it's a CKI issue unless you all say otherwise.
Hi,
yes, we finally got the builds fixed and are able to run the testing, and immediately hit the following Fedora bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2074083
We're looking into what exactly went wrong, the initial suspect is that the bug caused aborted test runs which confused the reporting system. Sorry about that, and thank you for reaching out about the problem!
The listed failures are actual failures (both test and kernel bugs), but not specific to the stable tree. They were already reported to the relevant places. If you wish, you can look into the details in the provided DataWarehouse link.
Actually, we hit a panic that we don't know if it has been reported yet. More logs at [1].
[ 346.728135] CPU: 12 PID: 158 Comm: kworker/12:1H Tainted: G I 5.17.2 #1 [ 346.770889] Hardware name: HP ProLiant SL390s G7/, BIOS P69 07/02/2013 [ 346.805535] Workqueue: kblockd blk_mq_run_work_fn [ 346.827834] RIP: 0010:__bfq_deactivate_entity+0x168/0x240 [ 346.855601] Code: 48 2b 41 28 48 85 c0 7e 05 49 89 5c 24 18 49 8b 44 24 08 4d 8d 74 24 08 48 85 c0 0f 84 d3 00 00 00 48 8b 7b 28 eb 03 48 89 c8 <48> 8b 48 28 48 8d 70 10 48 8d 50 08 48 29 f9 48 85 c9 48 0f 4f d6 [ 346.947892] RSP: 0018:ffffac0943f6bbe0 EFLAGS: 00010086 [ 346.973661] RAX: 9fa41f2000000000 RBX: ffff9ae8c9164748 RCX: 9fa41f2000000000 [ 347.009384] RDX: ffff9aeaed07c0a8 RSI: ffff9aeaed07c0a8 RDI: 0000000ae2080ce1 [ 347.044680] RBP: ffff9ae8c91646c0 R08: ffff9aeadd031960 R09: 0000004f9bf8c41b [ 347.080125] R10: 0000000000000001 R11: 0000000000000000 R12: ffff9aeadd031960 [ 347.116032] R13: 0000000000000001 R14: ffff9aeadd031968 R15: ffff9ae8cb750748 [ 347.150977] FS: 0000000000000000(0000) GS:ffff9aeacbb80000(0000) knlGS:0000000000000000 [ 347.198911] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 347.228754] CR2: 00007fb1e2c6ae14 CR3: 0000000340810005 CR4: 00000000000206e0 [ 347.268138] Call Trace: [ 347.281292] <TASK> [ 347.292058] bfq_deactivate_entity+0x50/0xc0 [ 347.313894] bfq_del_bfqq_busy+0x91/0x190 [ 347.335376] bfq_remove_request+0x124/0x340 [ 347.357453] ? bfq_may_expire_for_budg_timeout+0xa5/0x1c0 [ 347.385031] ? _raw_spin_unlock_irqrestore+0x25/0x40 [ 347.411908] ? bfq_bfqq_served+0x132/0x1a0 [ 347.433312] bfq_dispatch_request+0x44d/0x12e0 [ 347.454390] ? sbitmap_get+0x90/0x1a0 [ 347.472494] blk_mq_do_dispatch_sched+0x109/0x370 [ 347.496896] ? finish_task_switch.isra.0+0xc1/0x2f0 [ 347.520044] ? __switch_to+0x77/0x430 [ 347.537777] __blk_mq_sched_dispatch_requests+0xd8/0x120 [ 347.567004] blk_mq_sched_dispatch_requests+0x30/0x60 [ 347.592476] __blk_mq_run_hw_queue+0x34/0x90 [ 347.614232] process_one_work+0x1c7/0x380 [ 347.635369] worker_thread+0x4d/0x380 [ 347.652939] ? _raw_spin_lock_irqsave+0x25/0x50 [ 347.674477] ? process_one_work+0x380/0x380 [ 347.697082] kthread+0xe9/0x110 [ 347.712042] ? kthread_complete_and_exit+0x20/0x20 [ 347.735250] ret_from_fork+0x22/0x30 [ 347.753503] </TASK>
[1] https://datawarehouse.cki-project.org/kcidb/tests/3193432
Thanks, Bruno
We're working on transforming the email reports to include the known issue detection that is currently provided in the dashboard, it should be in place in the (hopefully) near future. That should also stabilize the emails.
Veronika
thanks,
greg k-h
linux-stable-mirror@lists.linaro.org
-
Bruno Goncalves -
CKI Project -
Greg KH -
Veronika Kabatova