From: cki-project@redhat.com
To: will@kernel.org, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org
Cc: jdoe@redhat.com
Subject: ❌ FAIL: Test report for for-kernelci (6.0.0-rc7, arm-next, bbed346d)
Date: Fri, 30 Sep 2022 17:50:03 -0000 [thread overview]
Message-ID: <82795.122093013500401292@us-mta-629.us.mimecast.lan> (raw)
Hi, we tested your kernel and here are the results:
Overall result: FAILED
Merge: OK
Compile: OK
Test: FAILED
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/54803
One or more kernel tests failed:
Unrecognized or new issues:
aarch64 - UPT smoke tests ending with WARN result
Logs: https://datawarehouse.cki-project.org/kcidb/tests/5319238
aarch64 - UPT smoke tests ending with FAIL result
Logs: https://datawarehouse.cki-project.org/kcidb/tests/5319239
If you find a failure unrelated to your changes, please tag it at https://datawarehouse.cki-project.org .
This will prevent the failures from being incorrectly reported in the future.
If you don't have permissions to tag an issue, you can contact the CKI team or
test maintainers.
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
`-'
______________________________________________________________________________
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2022-09-30 17:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=82795.122093013500401292@us-mta-629.us.mimecast.lan \
--to=cki-project@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=jdoe@redhat.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;
as well as URLs for NNTP newsgroup(s).