From: Veronika Kabatova <vkabatov@redhat.com>
To: Will Deacon <will@kernel.org>
Cc: catalin marinas <catalin.marinas@arm.com>,
Memory Management <mm-qe@redhat.com>,
Jeff Bastian <jbastian@redhat.com>,
CKI Project <cki-project@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: Mon, 19 Oct 2020 04:27:17 -0400 (EDT) [thread overview]
Message-ID: <1833539214.15129505.1603096037675.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20201016082105.GA6320@willie-the-truck>
----- Original Message -----
> From: "Will Deacon" <will@kernel.org>
> To: "CKI Project" <cki-project@redhat.com>
> Cc: "catalin marinas" <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
> Sent: Friday, October 16, 2020 10:21:05 AM
> Subject: Re: ❌ FAIL: Test report for kernel 5.9.0 (arm-next)
>
> 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)".
>
Hi,
I see a test timeout because it took too long which I don't think is
related to kernel (we've already submitted a bug to the test framework
to allow proper detection of it but it wasn't fixed yet, sorry!).
However, we're also hunting down a bug in mm/usercopy which is triggered
by stress-ng which we've seen so far on block and mainline, and the
subtest that triggers it wasn't ran due to the timeout. I resubmitted
the test job to check if your tree is affected as well and will let you
know if we see the panic.
Veronika
> > ❌ 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-19 8:30 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
2020-10-19 8:27 ` Veronika Kabatova [this message]
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=1833539214.15129505.1603096037675.JavaMail.zimbra@redhat.com \
--to=vkabatov@redhat.com \
--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=will@kernel.org \
/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).