[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180424174656.GA11717@roeck-us.net>
Date: Tue, 24 Apr 2018 10:46:56 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Naresh Kamboju <naresh.kamboju@...aro.org>,
open list <linux-kernel@...r.kernel.org>,
Shuah Khan <shuah@...nel.org>, patches@...nelci.org,
lkft-triage@...ts.linaro.org,
Ben Hutchings <ben.hutchings@...ethink.co.uk>,
linux- stable <stable@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>, tytso@....edu
Subject: Re: [PATCH 4.9 00/95] 4.9.96-stable review
On Tue, Apr 24, 2018 at 12:23:11PM -0500, Dan Rue wrote:
> On Tue, Apr 24, 2018 at 09:26:35AM +0200, Greg Kroah-Hartman wrote:
> > On Mon, Apr 23, 2018 at 05:25:53PM -0500, Dan Rue wrote:
> > > I made a few comments inline regarding the reported failures. Also, as
> > > this report is pushing 200 lines now with all of our tests and
> > > environments (about 8*22 test runs), I'm planning on making some changes
> > > in the next few weeks to make it more concise and useful. Any
> > > suggestions or feature requests are most welcome.
> >
> > How about only reporting problems? Having tests "pass" is the norm and
> > should always happen, right? That would make the reports smaller.
>
> I agree, though I would like to provide a bit of context so that people
> new to the process have some idea about testing breadth and depth - but
I did that initially, but found that it is only confusing. Sure, there
should be a means to look up the actual tests, but for the notification e-mail
only pass/fail is relevant.
I found that even "skipped" is confusing, because people started asking why
tests are being skipped.
Guenter
Powered by blists - more mailing lists