From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752742AbbJLT4I (ORCPT ); Mon, 12 Oct 2015 15:56:08 -0400 Received: from mail-oi0-f44.google.com ([209.85.218.44]:35970 "EHLO mail-oi0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752507AbbJLT4D (ORCPT ); Mon, 12 Oct 2015 15:56:03 -0400 MIME-Version: 1.0 In-Reply-To: References: <22034.43969.711116.77647@mariner.uk.xensource.com> From: "Luis R. Rodriguez" Date: Mon, 12 Oct 2015 12:55:41 -0700 X-Google-Sender-Auth: AWVktn0yOABPdqRFDKL8KpnwqKQ Message-ID: Subject: Re: Wiki for automatic reports / fixes To: Ian Jackson Cc: Fengguang Wu , Valentin Rothberg , Dan Carpenter , Mel Gorman , Steven Rostedt , Johannes Thumshirn , Konstantin Ryabitsev , Jonathan Corbet , Lars Kurth , Stefano Stabellini , Vitaly Kuznetsov , Robert Schweikert , ms@suse.de, Juergen Gross , "linux-kernel@vger.kernel.org" , Joerg Roedel , "linux-doc@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 5, 2015 at 10:03 AM, Luis R. Rodriguez wrote: > On Mon, Oct 5, 2015 at 9:56 AM, Ian Jackson wrote: >> Luis R. Rodriguez writes ("Wiki for automatic reports / fixes"): >> [...] >>> While discussing expectations and information about >>> reports over these with Valentin it occurred to me information about >>> all these may be scattered separately and some developers may be >>> surprised when they first get reports / fixes from these sorts of >>> testing systems and that perhaps it may be useful if we had a single >>> wiki entry point where we could refer folks to the different ongoing >>> testing infrastructures out there working upstream. >>> >>> If we could piggy back off of an already existing wiki then great, but >>> if not I was thinking something off of wiki.kernel.org might be good. >>> How about tests.wiki.kernel.org ? If such projects don't have a wiki >>> they could perhaps use pages off of tests.wiki.kernel.org to elaborate >>> and set expectations straight. Thoughts? >> >> To clarify what I think you are suggesting, is to create a new wiki or >> wiki page which gives information about automatic tests that are >> performed on upstream (or going-upstream) Linux branches ? > > That's right, as it stands we have a slew of folks doing a series of > battery of tests on either linux-next or other branches, and > developers / maintainers get e-mails about this. Typically one becomes > aware of these tests through experience and in dealing with reports > but other times one may not even be aware of ongoing effort on this > front, such was the case of Valentin's dead code analysis with > undertaker. Knowing what existing work is being done can and could be > used can also save people from re-inventing the wheel, but also and > most importantly collaborate. > >> I think this is a good idea. I'm not sure how much information we >> need for each tester, but a page for each would be about right. > > Sure, I figure if each tester framework has its own dedicated page we > can at least refer to it, but a basic page which describes general > coverage / mailing lists / contact info / and what to expect might be > useful. As it stands most of this is just tribal knowledge. OK I'll poke and see if we can get this created. Luis