Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.13.13-200.fc34
Task URL:
https://koji.fedoraproject.org/koji/taskinfo?taskID=74567467
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
๐ฅ stress: stress-ng
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
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:
โก 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
โกโกโก Reboot test
โกโกโก xfstests - ext4
โกโกโก xfstests - xfs
โกโกโก Storage: swraid mdadm raid_module test
๐ง โกโกโก xfstests - btrfs
๐ง โกโกโก Storage blktests
๐ง โกโกโก Storage block - filesystem fio test
๐ง โกโกโก Storage block - queue scheduler test
๐ง โกโกโก Storage nvme - tcp
๐ง โกโกโก storage: software RAID testing
๐ง โกโกโก stress: stress-ng
Host 2:
โ
Boot test
โ
Reboot test
โ
ACPI table test
โ LTP
โ
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 3:
โ
Boot test
โ
Reboot test
โ
xfstests - ext4
โ
xfstests - xfs
โ
Storage: swraid mdadm raid_module test
๐ง โ
xfstests - btrfs
๐ง โ
Storage blktests
๐ง โ
Storage block - filesystem fio test
๐ง โ
Storage block - queue scheduler test
๐ง โ
Storage nvme - tcp
๐ง โ
storage: software RAID testing
๐ง ๐ฅ stress: stress-ng
ppc64le:
Host 1:
โ
Boot test
โ
Reboot test
โ
LTP
โ
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:
โ
Boot test
โ
Reboot test
โ
xfstests - ext4
โ
xfstests - xfs
โ
Storage: swraid mdadm raid_module test
๐ง โ
xfstests - btrfs
๐ง โ
Storage blktests
๐ง โ
Storage block - filesystem fio test
๐ง โ
Storage block - queue scheduler test
๐ง โ
Storage nvme - tcp
๐ง โ
Storage: lvm device-mapper test - upstream
๐ง โ
storage: software RAID testing
s390x:
Host 1:
โ
Boot test
โ
Reboot test
โ
LTP
โ
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:
โ
Boot test
โ
Reboot test
โ
Storage: swraid mdadm raid_module test
๐ง โ
Storage blktests
๐ง โ
Storage nvme - tcp
๐ง โ
stress: stress-ng
x86_64:
Host 1:
โ
Boot test
โ
Reboot test
โ
ACPI table test
โ
LTP
โ
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:
โ
Boot test
โ
Reboot test
โ
xfstests - ext4
โ
xfstests - xfs
โ
xfstests - nfsv4.2
โ
Storage: swraid mdadm raid_module test
๐ง โ
xfstests - btrfs
๐ง โ
xfstests - cifsv3.11
๐ง โ
Storage blktests
๐ง โ
Storage block - filesystem fio test
๐ง โ
Storage block - queue scheduler test
๐ง โ
Storage nvme - tcp
๐ง โ
Storage: lvm device-mapper test - upstream
๐ง โ
storage: software RAID testing
๐ง โ
stress: stress-ng
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 โฑ.