From: Baoquan He <bhe@redhat.com>
To: cki-project@redhat.com
Cc: llvm@lists.linux.dev, xiawu@redhat.com
Subject: Re: ❌ FAIL: Test report for master (6.0.0-rc4, mainline.kernel.org-clang, 0066f1b0)
Date: Thu, 8 Sep 2022 09:19:32 +0800 [thread overview]
Message-ID: <YxlDJCV6MTxogbbW@MiWiFi-R3L-srv> (raw)
In-Reply-To: <41701.122090715304311827@us-mta-647.us.mimecast.lan>
On 09/07/22 at 07:30pm, 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: afs: Return -EAGAIN, not -EREMOTEIO, when a file already locked
>
> You can find all the details about the test run at
> https://datawarehouse.cki-project.org/kcidb/checkouts/52740
>
> One or more kernel tests failed:
>
> Unrecognized or new issues:
> ppc64le - kdump - sysrq-c
> Logs: https://datawarehouse.cki-project.org/kcidb/tests/5069753
This is an old issue we have ever encountered in 5.17, no space left.
Please check below extract from taskout.log and the old gitlab ticket
issues. It's nothing much kdump side can do.
https://s3.us-east-1.amazonaws.com/arr-cki-prod-datawarehouse-public/datawarehouse-public/2022/09/07/redhat:632996638/build_ppc64le_redhat:632996638_ppc64le/tests/3/results_0001/job.02/recipes/12568764/tasks/6/logs/taskout.log
***extract from taskout.log
======extract from taskout.log
Sep 07 03:09:16 ibm-p9z-27-lp25.ibm2.lab.eng.bos.redhat.com dracut[1032]: *** Creating image file '/boot/initramfs-6.0.0-rc4kdump.img' ***
Sep 07 03:09:16 ibm-p9z-27-lp25.ibm2.lab.eng.bos.redhat.com kdumpctl[3700]: cp: error writing '/boot/initramfs-6.0.0-rc4kdump.img': No space left on device
Sep 07 03:09:16 ibm-p9z-27-lp25.ibm2.lab.eng.bos.redhat.com kdumpctl[999]: dracut: dracut: creation of /boot/initramfs-6.0.0-rc4kdump.img failed
Sep 07 03:09:16 ibm-p9z-27-lp25.ibm2.lab.eng.bos.redhat.com dracut[1032]: dracut: creation of /boot/initramfs-6.0.0-rc4kdump.img failed
Sep 07 03:09:16 ibm-p9z-27-lp25.ibm2.lab.eng.bos.redhat.com kdumpctl[724]: kdump: mkdumprd: failed to make kdump initrd
Sep 07 03:09:16 ibm-p9z-27-lp25.ibm2.lab.eng.bos.redhat.com kdumpctl[724]: kdump: Starting kdump: [FAILED]
Sep 07 03:09:16 ibm-p9z-27-lp25.ibm2.lab.eng.bos.redhat.com systemd[1]: kdump.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 03:09:16 ibm-p9z-27-lp25.ibm2.lab.eng.bos.redhat.com systemd[1]: kdump.service: Failed with result 'exit-code'.
Sep 07 03:09:16 ibm-p9z-27-lp25.ibm2.lab.eng.bos.redhat.com systemd[1]: Failed to start kdump.service - Crash recovery kernel arming.
Sep 07 03:09:16 ibm-p9z-27-lp25.ibm2.lab.eng.bos.redhat.com systemd[1]: kdump.service: Consumed 42.273s CPU time.
==========
***The old issue in 5.17 which warned no space left on ppc64le
====
kdump - sysrq-c: failed to save a vmcore: No space left on device
https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/1163#note_1011391562
[ppc64le] Boot test: tar: boot/vmlinux-kbuild-5.17.0: Cannot write: No space left on device
https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/1047
next parent reply other threads:[~2022-09-08 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41701.122090715304311827@us-mta-647.us.mimecast.lan>
2022-09-08 1:19 ` Baoquan He [this message]
2022-09-07 19:30 ❌ FAIL: Test report for master (6.0.0-rc4, mainline.kernel.org-clang, 0066f1b0) 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=YxlDJCV6MTxogbbW@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=cki-project@redhat.com \
--cc=llvm@lists.linux.dev \
--cc=xiawu@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