From: Jan Stancek <jstancek@redhat.com>
To: CKI Project <cki-project@redhat.com>
Cc: catalin marinas <catalin.marinas@arm.com>,
Memory Management <mm-qe@redhat.com>,
will@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: ❌ FAIL: Test report for kernel 5.8.0-rc1-b9249cb.cki (arm-next)
Date: Thu, 18 Jun 2020 02:07:55 -0400 (EDT) [thread overview]
Message-ID: <163954071.16503342.1592460475593.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <cki.72F10DD5A2.1F8H07UJY5@redhat.com>
----- Original Message -----
>
> Hello,
>
> 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: b9249cba25a5 - arm64: bti: Require clang >= 10.0.1 for
> in-kernel BTI support
>
> 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://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawarehouse/2020/06/17/602184
>
> One or more kernel tests failed:
>
> aarch64:
> ❌ LTP
mknod07 - updated
https://github.com/linux-test-project/ltp/commit/13fcfa2d6bdd1fb71c4528b47170e8e8fb3a8a32
setns01 - Christian posted a patch
https://lore.kernel.org/lkml/20200616225612.4068799-1-christian.brauner@ubuntu.com/
_______________________________________________
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-06-18 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 22:51 ❌ FAIL: Test report for kernel 5.8.0-rc1-b9249cb.cki (arm-next) CKI Project
2020-06-18 6:07 ` Jan Stancek [this message]
2020-06-18 7:22 ` Will Deacon
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=163954071.16503342.1592460475593.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=cki-project@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).