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