All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: cki-project@redhat.com
Cc: haliu@redhat.com, bgoncalv@redhat.com, xiawu@redhat.com,
	xzhou@redhat.com, llvm@lists.linux.dev, yizhan@redhat.com,
	jiji@redhat.com, yiche@redhat.com, zlang@redhat.com,
	yiyan@redhat.com
Subject: Re: ❌ FAIL (SKIPPED 49 of 328): Test report for master (6.5.0-rc1, mainline.kernel.org-clang, bde7f150)
Date: Tue, 18 Jul 2023 11:01:03 +0800	[thread overview]
Message-ID: <ZLYAb/03CSYZWW1K@MiWiFi-R3L-srv> (raw)
In-Reply-To: <39782.123071511204000362@us-mta-517.us.mimecast.lan>

On 07/15/23 at 03:20pm, cki-project@redhat.com wrote:
...snip...
>          ppc64le - kdump - sysrq-c
>                    Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784963
>                    Non-passing subtests:
>                        ❌ FAIL /kdump/crash-sysrq-c
>          ppc64le - kdump - file-load
>                    Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784964
>                    Non-passing subtests:
>                        ❌ FAIL /kdump/crash-sysrq-c

The test_console.log and console.log are all empty. However, I suspect
it's same issue as below bug. And all ppc64le kdump failures should be
the same issue observed on 6.5-rc1+.

Bug 2222526 - kdump failed with the error "Cannot open /proc/vmcore: No such file or directory"


       reply	other threads:[~2023-07-18  3:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <39782.123071511204000362@us-mta-517.us.mimecast.lan>
2023-07-18  3:01 ` Baoquan He [this message]
2023-07-15 15:20 ❌ FAIL (SKIPPED 49 of 328): Test report for master (6.5.0-rc1, mainline.kernel.org-clang, bde7f150) 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=ZLYAb/03CSYZWW1K@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=bgoncalv@redhat.com \
    --cc=cki-project@redhat.com \
    --cc=haliu@redhat.com \
    --cc=jiji@redhat.com \
    --cc=llvm@lists.linux.dev \
    --cc=xiawu@redhat.com \
    --cc=xzhou@redhat.com \
    --cc=yiche@redhat.com \
    --cc=yiyan@redhat.com \
    --cc=yizhan@redhat.com \
    --cc=zlang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.