Skip to contentSkip to conversation

❌ FAIL: Test report for kernel 5.13.0-rc3 (arm-next, c4681547)

DISCUSSION CKI Project 2 participants 2 messages May 25, 2021

lore
Share & tools
lore
#0 lore raw

Hello,

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

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
Commit: c4681547bcce - Linux 5.13-rc3

The results of these automated tests are provided below.

Overall result: FAILED (see details below)
Merge: OK
Compile: OK
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/05/24/308428205

One or more kernel tests failed:

aarch64:
❌ LTP
💥 Storage blktests

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 1 architecture:

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

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

aarch64:
Host 1:
✅ Boot test
✅ ACPI table test
✅ ACPI enabled test
❌ LTP
✅ CIFS Connectathon
✅ POSIX pjd-fstest suites
✅ Loopdev Sanity
✅ jvm - jcstress tests
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility) ✅ Networking bridge: sanity
✅ Ethernet drivers 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 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 ✅ Libkcapi AF_ALG test
✅ pciutils: update pci ids test
✅ ALSA PCM loopback test
✅ ALSA Control (mixer) Userspace Element test ✅ storage: SCSI VPD
✅ trace: ftrace/tracer
🚧 ✅ xarray-idr-radixtree-test
🚧 ✅ i2c: i2cdetect sanity
🚧 ✅ Firmware test suite
🚧 ✅ Memory function: kaslr
🚧 ✅ audit: audit testsuite 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.

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

Host 3:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ selinux-policy: serge-testsuite
✅ storage: software RAID testing
✅ Storage: swraid mdadm raid_module test
🚧 ✅ xfstests - btrfs
🚧 ✅ IPMI driver test
🚧 ✅ IPMItool loop stress test
🚧 💥 Storage blktests
🚧 ⚡⚡⚡ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ Storage nvme - tcp
🚧 ⚡⚡⚡ Storage: lvm device-mapper test
🚧 ⚡⚡⚡ 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 ⏱.

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

#1 lore raw
Quoted 20 lines · 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/arm64/linux.git

            Commit: c4681547bcce - Linux 5.13-rc3

The results of these automated tests are provided below.

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

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

Quoted 7 lines

https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/05/24/308428205

One or more kernel tests failed:

    aarch64:
     ? LTP
    ------------- 8< -------------
    81 tst_test.c:899: TINFO: Trying FUSE...
    82 tst_test.c:1311: TINFO: Timeout per run is 0h 05m 00s

    83 statx04.c:44: TPASS: sys_statx(AT_FDCWD, mntpoint/test_dir1, 0, 0,

&buf)
84 statx04.c:53: TFAIL: STATX_ATTR_COMPRESSED flag is not set 85 statx04.c:58: TFAIL: STATX_ATTR_APPEND flag is not set 86 statx04.c:63: TFAIL: STATX_ATTR_IMMUTABLE flag is not set 87 statx04.c:68: TFAIL: STATX_ATTR_NODUMP flag is not set

88 statx04.c:77: TPASS: sys_statx(AT_FDCWD, mntpoint/test_dir2, 0, 0,
&buf)
89 statx04.c:86: TPASS: STATX_ATTR_COMPRESSED flag is not set 90 statx04.c:91: TPASS: STATX_ATTR_APPEND flag is not set 91 statx04.c:96: TPASS: STATX_ATTR_IMMUTABLE flag is not set 92 statx04.c:101: TPASS: STATX_ATTR_NODUMP flag is not set
---------------------------------

This failure is likely the 'STATX_ATTR_*' flags unsupported with the FUSE issue.
We may need to fix it in the test.

Btw, I found there is a patch helping check the flag before using it. But I don't
know why we didn't merge it@that moment.
https://lists.linux.it/pipermail/ltp/2019-October/014123.html

Signature · 5 lines
Regards,
Li Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210525/cef86be4/attachment.htm>