From: Will Deacon <will@kernel.org>
To: CKI Project <cki-project@redhat.com>
Cc: Rachel Sibley <rasibley@redhat.com>,
catalin.marinas@arm.com, Memory Management <mm-qe@redhat.com>,
Jeff Bastian <jbastian@redhat.com>,
Jan Stancek <jstancek@redhat.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: ❌ FAIL: Test report for kernel 5.9.0 (arm-next)
Date: Fri, 16 Oct 2020 09:21:05 +0100 [thread overview]
Message-ID: <20201016082105.GA6320@willie-the-truck> (raw)
In-Reply-To: <cki.4C7DD4FC5D.QINZ08MDCW@redhat.com>
On Fri, Oct 16, 2020 at 03:48:13AM -0000, CKI Project wrote:
> 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: 51d96ff83ed7 - 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://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2020/10/15/615400
>
> One or more kernel tests failed:
>
> aarch64:
> ❌ stress: stress-ng
There's an interested WARN from the scheduler in the stress-ng run, but the
failures look more like they're related to the infrastructure because all of
the invocations seem to be saying "(Expected 0,2,3, got 0)".
> ❌ LTP
This looks like a broken setup:
7 RTNETLINK answers: Operation not permitted
8 netns_breakns_ns_exec_ipv4_ioctl 1 TBROK: unable to create veth pair devices
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-10-16 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 3:48 ❌ FAIL: Test report for kernel 5.9.0 (arm-next) CKI Project
2020-10-16 8:21 ` Will Deacon [this message]
2020-10-19 8:27 ` Veronika Kabatova
2020-10-19 10:29 ` Veronika Kabatova
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=20201016082105.GA6320@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=jbastian@redhat.com \
--cc=jstancek@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mm-qe@redhat.com \
--cc=rasibley@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