stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Hangbin Liu <haliu@redhat.com>
Cc: CKI Project <cki-project@redhat.com>,
	Linux Stable maillist <stable@vger.kernel.org>,
	netdev@vger.kernel.org, Jan Stancek <jstancek@redhat.com>,
	Xiumei Mu <xmu@redhat.com>, David Howells <dhowells@redhat.com>,
	linux-afs@lists.infradead.org
Subject: Re: ❌ FAIL: Stable queue: queue-5.2
Date: Tue, 10 Sep 2019 09:58:10 +0100	[thread overview]
Message-ID: <20190910085810.GA3593@kroah.com> (raw)
In-Reply-To: <20190910081956.GG22496@dhcp-12-139.nay.redhat.com>

On Tue, Sep 10, 2019 at 04:19:56PM +0800, Hangbin Liu wrote:
> On Wed, Aug 28, 2019 at 08:36:14AM -0400, CKI Project wrote:
> > 
> > Hello,
> > 
> > We ran automated tests on a patchset that was proposed for merging into this
> > kernel tree. The patches were applied to:
> > 
> >        Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
> >             Commit: f7d5b3dc4792 - Linux 5.2.10
> > 
> > The results of these automated tests are provided below.
> > 
> >     Overall result: FAILED (see details below)
> >              Merge: OK
> >            Compile: OK
> >              Tests: FAILED
> > 
> > All kernel binaries, config files, and logs are available for download here:
> > 
> >   https://artifacts.cki-project.org/pipelines/128519
> > 
> > 
> > 
> > One or more kernel tests failed:
> > 
> >   x86_64:
> >     ❌ Networking socket: fuzz
> 
> Sorry, maybe the info is a little late, I just found the call traces for this
> failure.

And this is no longer failing?

What is the "fuzz" test?

greg k-h

  reply	other threads:[~2019-09-10  8:58 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 12:36 ❌ FAIL: Stable queue: queue-5.2 CKI Project
2019-09-10  8:19 ` Hangbin Liu
2019-09-10  8:58   ` Greg KH [this message]
2019-09-10  9:30     ` Hangbin Liu
2019-09-10  9:40       ` Hangbin Liu
2019-09-10 10:52         ` Sasha Levin
  -- strict thread matches above, loose matches on Subject: below --
2019-09-19 12:42 CKI Project
2019-09-19 12:57 ` Greg KH
2019-09-07 11:48 CKI Project
2019-09-04  5:31 CKI Project
2019-09-04 21:40 ` Rachel Sibley
2019-08-30 23:41 CKI Project
2019-08-27 10:54 CKI Project
2019-08-26 22:06 CKI Project
2019-08-27 14:58 ` Rachel Sibley
2019-08-26 20:33 CKI Project
2019-08-26 21:00 ` Major Hayden
2019-08-25 14:37 CKI Project
2019-08-25 14:41 ` Greg KH
2019-08-26  8:23   ` Nikolai Kondrashov
2019-08-26  8:33     ` Greg KH
2019-08-26  9:13       ` Nikolai Kondrashov
2019-08-26  9:40         ` Nikolai Kondrashov
2019-08-26 11:12           ` Nikolai Kondrashov
2019-08-26 11:39             ` Nikolai Kondrashov
2019-08-26 13:33               ` Sasha Levin
2019-08-27 13:10                 ` Nikolai Kondrashov
2019-08-22 22:48 CKI Project
2019-08-22 23:37 ` Greg KH
2019-08-23  6:57   ` Jan Stancek
2019-08-23 15:38     ` Sasha Levin
2019-08-23  2:19 ` ? " Murphy Zhou
2019-08-18 21:09  " CKI Project
2019-08-18 14:27 CKI Project
2019-08-18 14:05 CKI Project
2019-08-18 14:20 ` Greg KH
2019-08-18 12:00 CKI Project
2019-08-18 16:59 ` Ondrej Mosnacek

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=20190910085810.GA3593@kroah.com \
    --to=greg@kroah.com \
    --cc=cki-project@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=haliu@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=xmu@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;
as well as URLs for NNTP newsgroup(s).