Re: ❌ FAIL: Test report for kernel 5.12.0-rc4 (arm-next, a61be843)
Veronika Kabatova
vkabatov at redhat.com
Mon Apr 12 10:44:00 BST 2021
----- Original Message -----
> From: "CKI Project" <cki-project at redhat.com>
> To: skt-results-master at redhat.com, will at kernel.org, "catalin marinas" <catalin.marinas at arm.com>,
> linux-arm-kernel at lists.infradead.org
> Cc: "Jianlin Shi" <jishi at redhat.com>, "Jianwen Ji" <jiji at redhat.com>, "Jeff Bastian" <jbastian at redhat.com>, "Hangbin
> Liu" <haliu at redhat.com>
> Sent: Saturday, April 10, 2021 1:40:34 AM
> Subject: ❌ FAIL: Test report for kernel 5.12.0-rc4 (arm-next, a61be843)
>
>
> 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: a61be843e1b1 - Merge branch 'for-next/fixes' 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:
>
> https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/04/09/284003294
>
> One or more kernel tests failed:
>
> aarch64:
> ❌ Networking tunnel: geneve basic test
>
Hi, this is still the same issue as previously reported, on a same commit.
We moved the pipelines to run on gitlab.com and it didn't occur to us to
turn off reporting for the initial runs there /facepalm
Sorry about the repeated notification!
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 -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
> 🚧 ✅ i2c: i2cdetect sanity
> 🚧 ✅ Firmware test suite
> 🚧 ✅ Memory function: kaslr
> 🚧 ✅ audit: audit testsuite test
>
> Host 2:
> ✅ 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 ⏱.
>
>
>
More information about the linux-arm-kernel
mailing list