[LTP] 💥 PANICKED: Test report for kernel 5.6.0-rc7-76ccd23.cki (mainline.kernel.org)
Rachel Sibley
rasibley@redhat.com
Tue Mar 24 20:44:22 CET 2020
On 3/24/20 2:51 PM, CKI Project wrote:
>
> Hello,
>
> We ran automated tests on a recent commit from this kernel tree:
>
> Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> Commit: 76ccd234269b - Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
>
> The results of these automated tests are provided below.
>
> Overall result: FAILED (see details below)
> Merge: OK
> Compile: OK
> Tests: PANICKED
>
> 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/03/24/503583
>
> One or more kernel tests failed:
>
> x86_64:
> 💥 xfstests - ext4
> 💥 LTP
Sorry for all the panic emails, this is caused by a known issue which is not yet merged
into Linus tree, patches were submitted last Friday for linux-block:
https://lore.kernel.org/lkml/20200321094521.85986-2-paolo.valente@linaro.org/
I've temporarily disabled cc'ing LTP ML for now while we investigate a better
solution to report known issues properly.
>
> 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:
>
> x86_64:
> make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg
>
>
> Hardware testing
> ----------------
> We booted each kernel and ran the following tests:
>
> x86_64:
> Host 1:
> ✅ Boot test
> ✅ selinux-policy: serge-testsuite
> ✅ lvm thinp sanity
> ✅ storage: software RAID testing
> ✅ stress: stress-ng
> 🚧 💥 xfstests - ext4
> 🚧 ⚡⚡⚡ xfstests - xfs
> 🚧 ⚡⚡⚡ IOMMU boot test
> 🚧 ⚡⚡⚡ IPMI driver test
> 🚧 ⚡⚡⚡ IPMItool loop stress test
> 🚧 ⚡⚡⚡ power-management: cpupower/sanity test
> 🚧 ⚡⚡⚡ Storage blktests
>
> Host 2:
> ✅ Boot test
> ✅ Storage SAN device stress - megaraid_sas
>
> Host 3:
> ✅ Boot test
> ✅ Storage SAN device stress - mpt3sas driver
>
> Host 4:
> ✅ Boot 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 MACsec: sanity
> ⚡⚡⚡ Networking socket: fuzz
> ⚡⚡⚡ Networking sctp-auth: sockopts test
> ⚡⚡⚡ 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
> ⚡⚡⚡ httpd: mod_ssl smoke sanity
> ⚡⚡⚡ tuned: tune-processes-through-perf
> ⚡⚡⚡ pciutils: sanity smoke test
> ⚡⚡⚡ ALSA PCM loopback test
> ⚡⚡⚡ ALSA Control (mixer) Userspace Element test
> ⚡⚡⚡ Usex - version 1.9-29
> ⚡⚡⚡ storage: SCSI VPD
> ⚡⚡⚡ trace: ftrace/tracer
> 🚧 ⚡⚡⚡ CIFS Connectathon
> 🚧 ⚡⚡⚡ POSIX pjd-fstest suites
> 🚧 ⚡⚡⚡ jvm - DaCapo Benchmark Suite
> 🚧 ⚡⚡⚡ jvm - jcstress tests
> 🚧 ⚡⚡⚡ Memory function: kaslr
> 🚧 ⚡⚡⚡ LTP: openposix test suite
> 🚧 ⚡⚡⚡ Networking vnic: ipvlan/basic
> 🚧 ⚡⚡⚡ audit: audit testsuite test
> 🚧 ⚡⚡⚡ iotop: sanity
> 🚧 ⚡⚡⚡ storage: dm/common
>
> Test sources: https://github.com/CKI-project/tests-beaker
> 💚 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 ltp
mailing list