From: cki-project@redhat.com
To: will@kernel.org, linux-arm-kernel@lists.infradead.org,
catalin.marinas@arm.com
Subject: ❌ FAIL: Test report for for-kernelci (6.13.0-rc3, upstream-arm-next, 06a57361)
Date: Thu, 19 Dec 2024 23:12:08 -0000 [thread overview]
Message-ID: <64955.124121918121002524@us-mta-554.us.mimecast.lan> (raw)
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: Merge branch 'for-next/core' into for-kernelci
You can find all the details about the test run at
https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1596629923
One or more kernel builds failed:
Builds that are failing to boot:
aarch64 - https://datawarehouse.cki-project.org/kcidb/builds/redhat:1596629923-aarch64-kernel
If you find a failure unrelated to your changes, please ask the test maintainer to review it.
This will prevent the failures from being incorrectly reported in the future.
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
next reply other threads:[~2024-12-19 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 23:12 cki-project [this message]
2024-12-20 12:35 ` ❌ FAIL: Test report for for-kernelci (6.13.0-rc3, upstream-arm-next, 06a57361) Will Deacon
[not found] ` <CAMj1kXENrzsF6JzvbGSwiJT5nupfJbij86zp0k2+YbqUCqvqNA@mail.gmail.com>
[not found] ` <CAMj1kXGx+Li4qwh_05Uf-aTtEOLSThv8o3JjKgWrPp9t8rqQyg@mail.gmail.com>
2024-12-20 13:25 ` Will Deacon
2024-12-20 13:43 ` Will Deacon
2024-12-20 22:35 ` Konrad Dybcio
2024-12-20 22:36 ` Konrad Dybcio
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=64955.124121918121002524@us-mta-554.us.mimecast.lan \
--to=cki-project@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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