From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id DD4B7DB8 for ; Tue, 11 Sep 2018 16:49:40 +0000 (UTC) Received: from mail-pf1-f194.google.com (mail-pf1-f194.google.com [209.85.210.194]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E3C74716 for ; Tue, 11 Sep 2018 16:49:39 +0000 (UTC) Received: by mail-pf1-f194.google.com with SMTP id u24-v6so12505375pfn.13 for ; Tue, 11 Sep 2018 09:49:39 -0700 (PDT) Sender: Guenter Roeck Date: Tue, 11 Sep 2018 09:49:38 -0700 From: Guenter Roeck To: Stephen Rothwell Message-ID: <20180911164938.GB8284@roeck-us.net> References: <20180907004944.GD16300@sasha-vm> <20180907014930.GE16300@sasha-vm> <20180907145437.GF16300@sasha-vm> <20180910194310.GV16300@sasha-vm> <20180910164519.6cbcc116@vmware.local.home> <20180910212019.GA32269@roeck-us.net> <20180911104339.46143f61@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180911104339.46143f61@canb.auug.org.au> Cc: ksummit Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug-introducing patches List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Sep 11, 2018 at 10:43:39AM +1000, Stephen Rothwell wrote: > Hi Guenter, > > On Mon, 10 Sep 2018 14:20:19 -0700 Guenter Roeck wrote: > > > > On Mon, Sep 10, 2018 at 04:45:19PM -0400, Steven Rostedt wrote: > > > > > > The best we can do is make the automated testing of linux-next better > > > such that there's less -rc5 patches that need to go in in the first > > > place. > > > > > > > Would that help ? -next has been more or less unusable for a week or so. > > Maybe it is just a bad time (it hasn't been as bad as it is right now > > for quite some time), but > > > > Build results: > > total: 135 pass: 133 fail: 2 > > Qemu test results: > > total: 315 pass: 112 fail: 203 > > I assume that most of that is the mount api changes. I also assume you > have reported these? > I think so. I just noticed that the failure pattern changed yesterday, and did not have time to run bisect. So, no, I have not reported this specific failure. > > on next-20180910 doesn't really make me very confident that useful regression > > tests on -next are even possible. it seems to me that -next is quite often > > used as dumping ground for sparsely tested changes, and is far from "ready > > for upstream". > > Well, we do get some of that, but also some things are harder to test > in isolation. > -- > Cheers, > Stephen Rothwell