From: Will Deacon <will@kernel.org>
To: cki-project@redhat.com
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: ❌ FAIL (MISSED 7 of 7): Test report for for-kernelci (6.12.0-rc1, arm-next, 2d8bce6e)
Date: Mon, 14 Oct 2024 13:50:00 +0100 [thread overview]
Message-ID: <20241014124959.GA17324@willie-the-truck> (raw)
In-Reply-To: <56533.124101100220700918@us-mta-586.us.mimecast.lan>
Hi CKI folks,
On Fri, Oct 11, 2024 at 04:22:05AM -0000, cki-project@redhat.com wrote:
> Hi, we tested your kernel and here are the results:
>
> Overall result: FAILED
> Merge: OK
> Compile: OK
> Test: FAILED (Did not boot)
>
>
> Kernel information:
> Commit message: KVM: arm64: Shave a few bytes from the EL2 idmap code
>
> You can find all the details about the test run at
> https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1490716817
>
> One or more kernel builds failed:
> Builds that are failing to boot:
> aarch64 - https://datawarehouse.cki-project.org/kcidb/builds/redhat:1490716817-aarch64-kernel
>
> Tests that were not ran because of internal issues:
> Boot test [aarch64]
Do you have any more information about this "boot test" failure, please?
If I click through to the "Boot test" tests (e.g. [1]) then the
"console.log" file is empty.
The build log has a funny error about certificates:
00:00:04 Additional X.509 keys for default system keyring (SYSTEM_TRUSTED_KEYS) [] (NEW)
00:00:04 Error in reading or end of file.
but I don't know whether or not that is significant.
Cheers,
Will
[1] https://datawarehouse.cki-project.org/kcidb/tests/14736505
next prev parent reply other threads:[~2024-10-14 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 4:22 ❌ FAIL (MISSED 7 of 7): Test report for for-kernelci (6.12.0-rc1, arm-next, 2d8bce6e) cki-project
2024-10-14 12:50 ` Will Deacon [this message]
[not found] ` <CAPo4OxSr9=cFK1MujqgG-jOWygnZ44TWe8K3Fj1Q8pbLCNQNEw@mail.gmail.com>
2024-10-14 16:15 ` 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=20241014124959.GA17324@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