Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: CKI Project <cki-project@redhat.com>
Cc: skt-results-master@redhat.com, stable@vger.kernel.org,
	Memory Management <mm-qe@redhat.com>, Li Wang <liwang@redhat.com>,
	Jan Stancek <jstancek@redhat.com>,
	Guangwu Zhang <guazhang@redhat.com>,
	Filip Suba <fsuba@redhat.com>,
	Fendy Tjahjadi <ftjahjad@redhat.com>,
	Yi Zhang <yizhan@redhat.com>, Changhui Zhong <czhong@redhat.com>,
	Bruno Goncalves <bgoncalv@redhat.com>
Subject: Re: ❌ FAIL: Test report for kernel 5.17.2 (stable-queue, eabfed45)
Date: Wed, 13 Apr 2022 08:23:55 +0200	[thread overview]
Message-ID: <YlZse4JgKRqMBdJ1@kroah.com> (raw)
In-Reply-To: <cki.LEF6Q6V9CU1O7JTZ58AW@redhat.com>

On Wed, Apr 13, 2022 at 06:03:14AM -0000, CKI Project wrote:
> 
> 
> Check out this report and any autotriaged failures in our web dashboard:
>     https://datawarehouse.cki-project.org/kcidb/checkouts/38921
> 
> Hello,
> 
> We ran automated tests on a recent commit from this kernel tree:
> 
>        Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>             Commit: eabfed45bc7c - io_uring: drop the old style inflight file tracking

It's alive!

> The results of these automated tests are provided below.
> 
>     Overall result: FAILED (see details below)
>              Merge: OK
>            Compile: OK
>              Tests: FAILED
>     Targeted tests: NO

But things are failing.

Is this the CKI tool's issue, or is it the patches in the stable queue's
issue?

Given that CKI has been dead for so long, I'll guess it's a CKI issue
unless you all say otherwise.

thanks,

greg k-h

  reply	other threads:[~2022-04-13  6:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  6:03 ❌ FAIL: Test report for kernel 5.17.2 (stable-queue, eabfed45) CKI Project
2022-04-13  6:23 ` Greg KH [this message]
2022-04-13 12:50   ` Veronika Kabatova
2022-04-13 15:33     ` Bruno Goncalves

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=YlZse4JgKRqMBdJ1@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bgoncalv@redhat.com \
    --cc=cki-project@redhat.com \
    --cc=czhong@redhat.com \
    --cc=fsuba@redhat.com \
    --cc=ftjahjad@redhat.com \
    --cc=guazhang@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=liwang@redhat.com \
    --cc=mm-qe@redhat.com \
    --cc=skt-results-master@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=yizhan@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