Re: ❌ FAIL: Test report for kernel 5.9.0-rc3-f75aef3.cki (arm-next)

[Veronika Kabatova]

----- Original Message -----
> From: "CKI Project" <cki-project at redhat.com>
> To: will at kernel.org, "catalin marinas" <catalin.marinas at arm.com>, linux-arm-kernel at lists.infradead.org
> Sent: Thursday, September 3, 2020 1:30:09 AM
> Subject: ❌ FAIL: Test report for kernel 5.9.0-rc3-f75aef3.cki	(arm-next)
> 
> 
> 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: f75aef392f86 - Linux 5.9-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://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawarehouse/2020/09/02/613175
> 
> One or more kernel tests failed:
> 
>     aarch64:
>      ❌ Boot test
> 

I went through the console logs and the last messages are all from EFI and
there is no kernel banner. I'm guessing the connection to the machine got
lost during that time. In any case, it's NOT a kernel problem but a problem
we need to do a better job of detecting (which is harder than it sounds),
sorry.


Veronika

> 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:
>        ✅ Boot test
>        ✅ ACPI table test
>        ✅ ACPI enabled test
>        ✅ Podman system integration test - as root
>        ✅ Podman system integration test - as user
>        ✅ LTP
>        ✅ Loopdev Sanity
>        ✅ 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 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
>        🚧 ✅ jvm - jcstress tests
>        🚧 ✅ Memory function: kaslr
>        🚧 ✅ Networking firewall: basic netfilter test
>        🚧 ✅ audit: audit testsuite test
>        🚧 ✅ trace: ftrace/tracer
>        🚧 ✅ kdump - kexec_boot
> 
>     Host 2:
>        ❌ Boot test
>        ⚡⚡⚡ xfstests - ext4
>        ⚡⚡⚡ xfstests - xfs
>        ⚡⚡⚡ selinux-policy: serge-testsuite
>        ⚡⚡⚡ storage: software RAID testing
>        ⚡⚡⚡ stress: stress-ng
>        🚧 ⚡⚡⚡ xfstests - btrfs
>        🚧 ⚡⚡⚡ IPMI driver test
>        🚧 ⚡⚡⚡ IPMItool loop stress test
>        🚧 ⚡⚡⚡ Storage blktests
> 
>   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 ⏱.
> 
> 
>