Re: ❌ FAIL: Test report for kernel 5.7.3-200.fc32 (fedora-32)

[Veronika Kabatova]

----- Original Message -----
>  From: "CKI Project" <cki-project(a)redhat.com&gt;
>  To: kernel(a)lists.fedoraproject.org
>  Sent: Thursday, June 18, 2020 2:45:10 AM
>  Subject: ❌ FAIL: Test report for kernel 5.7.3-200.fc32 (fedora-32)
>  
>  Hello jforbes,
>  
>  We ran automated tests on the following kernel build:
>  
>      Kernel package: kernel-5.7.3-200.fc32
>           COPR build ID: 1470174
>  
>  The results of these automated tests are provided below.
>  
>      Overall result: FAILED (see details below)
>               Tests: FAILED
>  
>  One or more kernel tests failed:
>  
>      x86_64:
>       ❌ Boot test
>       ❌ Boot test
>       ❌ Boot test
>  
>   
Hi,

this is a bug in our COPR pipelines. Please refer to the regular koji
test reports while we work through the issue, and sorry for the
inconvenience.

Veronika

>  
>  All kernel binaries, config files, and logs are available for download here:
>  
>   
> https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
>  
>  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.
>  For the full detail on our testing procedures, please scroll to the bottom of
>  this message.
>  
>          ,-.   ,-.
>         ( C ) ( K )  Continuous
>          `-',-.`-'   Kernel
>            ( I )     Integration
>             `-'
>  ______________________________________________________________________________
>  
>  Hardware testing
>  ----------------
>  We booted each kernel and ran the following tests:
>  
>    x86_64:
>      Host 1:
>         ❌ 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 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: sanity smoke 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 - DaCapo Benchmark Suite
>         🚧 ⚡⚡⚡ 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
>         🚧 ⚡⚡⚡ CPU: Frequency Driver Test
>         🚧 ⚡⚡⚡ CPU: Idle Test
>         🚧 ⚡⚡⚡ IOMMU boot test
>         🚧 ⚡⚡⚡ IPMI driver test
>         🚧 ⚡⚡⚡ IPMItool loop stress test
>         🚧 ⚡⚡⚡ power-management: cpupower/sanity test
>         🚧 ⚡⚡⚡ Storage blktests
>  
>      Host 3:
>         ❌ Boot test
>         🚧 ⚡⚡⚡ kdump - sysrq-c
>  
>    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 ⏱.
>  _______________________________________________
>  kernel mailing list -- kernel(a)lists.fedoraproject.org
>  To unsubscribe send an email to kernel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>