❌ FAIL: Test report for kernel 5.11.0-rc7 (arm-next)

CKI Project cki-project at redhat.com
Tue Feb 9 16:07:50 EST 2021


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: 4176e42aa565 - Merge branch 'for-next/cpufeature' into for-kernelci

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:


One or more kernel tests failed:

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

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

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

    Host 1:
       ✅ 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

    Host 2:
       ❌ Boot test
       ⚡⚡⚡ selinux-policy: serge-testsuite
       ⚡⚡⚡ storage: software RAID testing
       🚧 ⚡⚡⚡ xfstests - ext4
       🚧 ⚡⚡⚡ xfstests - xfs
       🚧 ⚡⚡⚡ 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: swraid mdadm raid_module 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 ⏱.

More information about the linux-arm-kernel mailing list