From: Will Deacon <will@kernel.org>
To: cki-project@redhat.com
Cc: bgoncalv@redhat.com, linux-arm-kernel@lists.infradead.org,
catalin.marinas@arm.com
Subject: Re: ❌ FAIL: Test report for for-kernelci (6.10.0-rc6, arm-next, fdd6064f)
Date: Tue, 2 Jul 2024 13:09:54 +0100 [thread overview]
Message-ID: <20240702120954.GA3542@willie-the-truck> (raw)
In-Reply-To: <84743.124070118021000123@us-mta-326.us.mimecast.lan>
On Mon, Jul 01, 2024 at 10:02:07PM -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
>
>
> Kernel information:
> Commit message: Merge remote-tracking branch 'tglx/devmsi-arm' into for-kernelci
>
> You can find all the details about the test run at
> https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1356144307
>
> One or more kernel tests failed:
> Unrecognized or new issues:
> Boot test
> aarch64
> Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1356144307-aarch64-kernel_upt_4
> Non-passing ran subtests:
> ❌ FAIL distribution/kpkginstall/journalctl-check
> Reboot test
> aarch64
> Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1356144307-aarch64-kernel_upt_10
> Non-passing ran subtests:
> ❌ FAIL misc/reboot-test/journalctl-check
I'm struggling to see the problem from the logs, but it could be that
it's hidden by all the Coresight sysfs errors (which I think came up
before and were attributed to buggy firmware?).
Will
prev parent reply other threads:[~2024-07-02 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 22:02 ❌ FAIL: Test report for for-kernelci (6.10.0-rc6, arm-next, fdd6064f) cki-project
2024-07-02 12:09 ` Will Deacon [this message]
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=20240702120954.GA3542@willie-the-truck \
--to=will@kernel.org \
--cc=bgoncalv@redhat.com \
--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