Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.16.19-200.fc35 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=85357231
The results of these automated tests are provided below.
Overall result: FAILED (see details below) Tests: FAILED
One or more kernel tests failed:
aarch64: ❌ LTP - syscalls
ppc64le: ❌ LTP - syscalls
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix...
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. For the full detail on our testing procedures, please scroll to the bottom of this message.
,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________
Hardware testing ---------------- We booted each kernel and ran the following tests:
aarch64: Host 1: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot 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 ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ NFS Connectathon
Host 2: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - nvmeof-mp
Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ lvm thinp sanity ✅ Storage: swraid mdadm raid_module test ✅ stress: stress-ng - interrupt ✅ stress: stress-ng - cpu ✅ stress: stress-ng - cpu-cache ✅ stress: stress-ng - memory 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage block - storage fio numa 🚧 ✅ storage: software RAID testing
ppc64le: Host 1: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot 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 ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon
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 ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ lvm thinp sanity ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage block - storage fio numa 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing
Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp
Host 4: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ lvm thinp sanity ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage block - storage fio numa 🚧 ✅ Storage: lvm device-mapper test - upstream 🚧 ✅ storage: software RAID testing
s390x: Host 1: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot 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 ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ NFS Connectathon
Host 2: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test ✅ Storage: swraid mdadm raid_module test ✅ stress: stress-ng - interrupt ✅ stress: stress-ng - cpu ✅ stress: stress-ng - cpu-cache ✅ stress: stress-ng - memory 🚧 ❌ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp
Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp
x86_64: Host 1: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ xfstests - nfsv4.2 ✅ lvm thinp sanity ✅ Storage: swraid mdadm raid_module test ✅ stress: stress-ng - interrupt ✅ stress: stress-ng - cpu ✅ stress: stress-ng - cpu-cache ✅ stress: stress-ng - memory 🚧 ✅ xfstests - btrfs 🚧 ✅ xfstests - cifsv3.11 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage block - storage fio numa 🚧 ✅ Storage: lvm device-mapper test - upstream 🚧 ✅ storage: software RAID testing
Host 2: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp
Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot 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 ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon
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 ⏱.
kernel@lists.fedoraproject.org