From: Will Deacon <will@kernel.org>
To: CKI Project <cki-project@redhat.com>
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: ❌ FAIL: Test report for kernel 5.11.0-rc7 (arm-next)
Date: Wed, 10 Feb 2021 09:29:46 +0000 [thread overview]
Message-ID: <20210210092946.GA28560@willie-the-truck> (raw)
In-Reply-To: <cki.8D1CB60FEC.K6NJMEFQPV@redhat.com>
Hi CKI folks,
Please can you help me with the error below?
On Tue, Feb 09, 2021 at 09:07:50PM -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: 4176e42aa565 - Merge branch 'for-next/cpufeature' 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/2021/02/09/623431
>
> One or more kernel tests failed:
>
> aarch64:
> ❌ Boot test
[...]
> Host 2:
> ❌ Boot test
> ⚡⚡⚡ selinux-policy: serge-testsuite
> ⚡⚡⚡ storage: software RAID testing
> 🚧 ⚡⚡⚡ xfstests - ext4
> 🚧 ⚡⚡⚡ xfstests - xfs
> 🚧 ⚡⚡⚡ xfstests - btrfs
> 🚧 ⚡⚡⚡ IPMI driver test
> 🚧 ⚡⚡⚡ IPMItool loop stress test
> 🚧 ⚡⚡⚡ Storage blktests
> 🚧 ⚡⚡⚡ Storage block - filesystem fio test
> 🚧 ⚡⚡⚡ Storage block - queue scheduler test
> 🚧 ⚡⚡⚡ Storage nvme - tcp
> 🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test
> 🚧 ⚡⚡⚡ stress: stress-ng
Which system (e.g. soc) is host 2 and are there are known infra issues at
the moment? I did push some changes which affect the early boot path, so we
may well be running into a kernel bug, but I'd just like to make sure before
we dive in trying to debug that, especially as we haven't seen failures on
other systems (and host 1 seems ok).
In the meantime, I'll push a new branch without those early changes to see
if that does any better.
Thanks,
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:[~2021-02-10 9:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 21:07 ❌ FAIL: Test report for kernel 5.11.0-rc7 (arm-next) CKI Project
2021-02-10 9:29 ` Will Deacon [this message]
2021-02-10 12:01 ` Veronika Kabatova
2021-02-10 15:24 ` Veronika Kabatova
2021-02-10 16:09 ` ❌ FAIL: Test report for kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 17:07 ` Veronika Kabatova
2021-02-10 17:31 ` ❌ FAIL: Test report for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 18:06 ` Veronika Kabatova
2021-02-10 18:56 ` ❌ FAIL: Test report?for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 19:31 ` Veronika Kabatova
2021-02-10 20:17 ` ❌ FAIL: Test?report?for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 20:32 ` Will Deacon
2021-02-11 10:46 ` Veronika Kabatova
2021-02-11 11:50 ` ❌ FAIL:?Test?report?for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-11 12:25 ` Veronika Kabatova
2021-02-15 13:13 ` Veronika Kabatova
2021-02-15 18:24 ` 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=20210210092946.GA28560@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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