From: Baoquan He <bhe@redhat.com>
To: cki-project@redhat.com
Cc: bgoncalv@redhat.com, yiyan@redhat.com, llvm@lists.linux.dev,
xiawu@redhat.com
Subject: Re: ❌ FAIL (SKIPPED 191 of 328): Test report for master (6.5.0-rc3, mainline.kernel.org-clang, 57012c57)
Date: Fri, 28 Jul 2023 12:57:08 +0800 [thread overview]
Message-ID: <ZMNKpJCzbAERwqp/@MiWiFi-R3L-srv> (raw)
In-Reply-To: <65365.123072800401200236@us-mta-556.us.mimecast.lan>
Hi CKI team,
On 07/28/23 at 04:40am, 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 tag 'net-6.5-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
>
> You can find all the details about the test run at
> https://datawarehouse.cki-project.org/kcidb/checkouts/97648
>
> One or more kernel tests failed:
> Unrecognized or new issues:
> x86_64 - kdump - sysrq-c
> Logs: https://datawarehouse.cki-project.org/kcidb/tests/8928580
> Non-passing subtests:
> ❌ FAIL /kdump/crash-sysrq-c
> x86_64 - kdump - file-load
> Logs: https://datawarehouse.cki-project.org/kcidb/tests/8928581
> Non-passing subtests:
> ❌ FAIL /kdump/crash-sysrq-c
> x86_64 (debug) - Boot test
> Logs: https://datawarehouse.cki-project.org/kcidb/tests/8928644
> Non-passing subtests:
> ❌ FAIL distribution/kpkginstall/journalctl-check
All these failure cases have empty console.log, there's no way to check
what's going on there. The empty console.log is related to 1st kernel,
there must something wrong withih it.
Thanks
Baoquan
next parent reply other threads:[~2023-07-28 4:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65365.123072800401200236@us-mta-556.us.mimecast.lan>
2023-07-28 4:57 ` Baoquan He [this message]
2023-07-28 6:54 ` ❌ FAIL (SKIPPED 191 of 328): Test report for master (6.5.0-rc3, mainline.kernel.org-clang, 57012c57) Bruno Goncalves
2023-07-31 6:40 ` Baoquan He
2023-07-28 4:40 cki-project
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=ZMNKpJCzbAERwqp/@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=bgoncalv@redhat.com \
--cc=cki-project@redhat.com \
--cc=llvm@lists.linux.dev \
--cc=xiawu@redhat.com \
--cc=yiyan@redhat.com \
/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