❌ FAIL: Test report for kernel 5.12.0-rc1 (arm-next)

[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: fe07bfda2fb9 - Linux 5.12-rc1

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/03/01/624694

One or more kernel tests failed:

    aarch64:
     ❌ ACPI table test
     ❌ Memory function: memfd_create
     ❌ AMTU (Abstract Machine Test Utility)
     ❌ Networking bridge: sanity
     ❌ Networking route: pmtu

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 -j30 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.

       ✅ 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
       ⚡⚡⚡ trace: ftrace/tracer
       🚧 ⚡⚡⚡ CIFS Connectathon
       🚧 ⚡⚡⚡ POSIX pjd-fstest suites
       🚧 ⚡⚡⚡ Firmware test suite
       🚧 ⚡⚡⚡ jvm - jcstress tests
       🚧 ⚡⚡⚡ Memory function: kaslr
       🚧 ⚡⚡⚡ Ethernet drivers sanity
       🚧 ⚡⚡⚡ Networking cki netfilter test
       🚧 ⚡⚡⚡ audit: audit testsuite 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 ⏱.