linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Veronika Kabatova <vkabatov@redhat.com>
To: CKI Project <cki-project@redhat.com>
Cc: Jianwen Ji <jiji@redhat.com>, Hangbin Liu <haliu@redhat.com>,
	catalin marinas <catalin.marinas@arm.com>,
	Yi Chen <yiche@redhat.com>, Xiumei Mu <xmu@redhat.com>,
	will@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: ❌ FAIL: Test report for kernel 5.5.0-rc6-b260f5e.cki	(arm-next)
Date: Fri, 17 Jan 2020 05:24:17 -0500 (EST)	[thread overview]
Message-ID: <1087562953.2535418.1579256657647.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <cki.9F6EEFCFB1.I2MBV5DGSX@redhat.com>



----- Original Message -----
> From: "CKI Project" <cki-project@redhat.com>
> To: will@kernel.org, "catalin marinas" <catalin.marinas@arm.com>, linux-arm-kernel@lists.infradead.org
> Cc: "Yi Chen" <yiche@redhat.com>, "Jianwen Ji" <jiji@redhat.com>, "Hangbin Liu" <haliu@redhat.com>, "Xiumei Mu"
> <xmu@redhat.com>
> Sent: Friday, January 17, 2020 4:35:27 AM
> Subject: ❌ FAIL: Test report for kernel 5.5.0-rc6-b260f5e.cki	(arm-next)
> 
> 
> Hello,
> 
> We ran automated tests on a recent commit from this kernel tree:
> 
>        Kernel repo:
>        git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
>             Commit: b260f5eb4e57 - Merge branch 'for-next/core' 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://artifacts.cki-project.org/pipelines/387219
> 
> One or more kernel tests failed:
> 
>     aarch64:
>      ❌ Networking UDP: socket
>      ❌ Networking ipsec: basic netns tunnel
> 

Hi,

after yesterday's discussions I thought I'd point it out specifically.
These tests did really report a failure and the results are not caused
by the infra issue we were talking about. I'm sure the test maintainers
can help with figuring out if this is something to be concerned with.


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: -j30 INSTALL_MOD_STRIP=1 targz-pkg
> 
> 
> Hardware testing
> ----------------
> We booted each kernel and ran the following tests:
> 
>   aarch64:
>     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 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
>        ✅ audit: audit testsuite test
>        ✅ httpd: mod_ssl smoke sanity
>        ✅ tuned: tune-processes-through-perf
>        ✅ ALSA PCM loopback test
>        ✅ ALSA Control (mixer) Userspace Element test
>        ✅ storage: SCSI VPD
>        ✅ trace: ftrace/tracer
>        🚧 ✅ CIFS Connectathon
>        🚧 ✅ POSIX pjd-fstest suites
>        🚧 ✅ jvm test suite
>        🚧 ✅ Memory function: kaslr
>        🚧 ✅ LTP: openposix test suite
>        🚧 ✅ Networking vnic: ipvlan/basic
>        🚧 ✅ iotop: sanity
>        🚧 ✅ Usex - version 1.9-29
>        🚧 ✅ storage: dm/common
> 
>     Host 2:
>        ✅ Boot test
>        ✅ xfstests: ext4
>        ✅ xfstests: xfs
>        ✅ selinux-policy: serge-testsuite
>        ✅ lvm thinp sanity
>        ✅ storage: software RAID testing
>        ✅ stress: stress-ng
>        🚧 ✅ IPMI driver test
>        🚧 ✅ IPMItool loop stress test
>        🚧 ✅ Storage blktests
> 
>   Test sources: https://github.com/CKI-project/tests-beaker
>     💚 Pull requests are welcome for new tests or improvements to existing
>     tests!
> 
> 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 are marked with ⏱. Reports for non-upstream kernels have
> a Beaker recipe linked to next to each host.
> 
> 
> 


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-01-17 10:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17  3:35 ❌ FAIL: Test report for kernel 5.5.0-rc6-b260f5e.cki (arm-next) CKI Project
2020-01-17 10:24 ` Veronika Kabatova [this message]
2020-01-17 10:34   ` ❌ FAIL: Test report for kernel 5.5.0-rc6-b260f5e.cki?(arm-next) Will Deacon
2020-01-17 10:57     ` Robin Murphy
2020-01-17 11:13       ` Will Deacon
2020-01-17 12:24         ` Robin Murphy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1087562953.2535418.1579256657647.JavaMail.zimbra@redhat.com \
    --to=vkabatov@redhat.com \
    --cc=catalin.marinas@arm.com \
    --cc=cki-project@redhat.com \
    --cc=haliu@redhat.com \
    --cc=jiji@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=will@kernel.org \
    --cc=xmu@redhat.com \
    --cc=yiche@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).