linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Mike Galbraith <mikeg@wen-online.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	stp@osdlab.org
Subject: Re: Regression testing of 2.4.x before release?
Date: Sun, 04 Nov 2001 09:58:39 -0800	[thread overview]
Message-ID: <3BE581CF.F1AABA25@kegel.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111040832060.364-100000@mikeg.weiden.de>

Mike Galbraith wrote:
> 
> On Sat, 3 Nov 2001, Dan Kegel wrote:
> 
> > I get the impression that Alan stress-tests his kernels
> > more than Linus does before releasing them.
> 
> That's _our_ collective job.  We're supposed to beat the snot out
> of the -pre kernels and report.  One guy can't cover effectively,
> even if his name is Linus "stress-testing is boring" Torvalds ;-)

I'm not saying Linus should do the testing.  

It's good that Linus is asking others to test with cerberus, as he
did in http://marc.theaimsgroup.com/?l=linux-kernel&m=100451768023436&w=2

It would be even better if Linus came out and stated that he would
refuse to call a kernel final if there is an outstanding report of 
it failing an agreed-upon set of stress tests.

And it would be *even better* if http://osdl.org/stp/ were used
to do stress testing in a nice, automated way on 1, 4, 8, and 16-cpu 
machines on release candidates.

Almost none of this requires any work by Linus.  All Linus has to
do is say "The 2.4.x kernels will pass stress tests before release",
and recruit someone to run his kernels through OSDL's STP in a
timely manner.

(I'd be happy to help if it weren't for my darn tendinitis, which
makes it hard even to stir up trouble on mailing lists these days.)
- Dan

       reply	other threads:[~2001-11-04 17:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0111040832060.364-100000@mikeg.weiden.de>
2001-11-04 17:58 ` Dan Kegel [this message]
2001-11-04 19:09   ` Regression testing of 2.4.x before release? Luigi Genoni
2001-11-05  1:51     ` Dan Kegel
2001-11-05 16:39     ` Timothy D. Witham
2001-11-12  6:24       ` Dan Kegel
2002-01-10 23:50         ` Daniel Phillips
2002-01-12  0:04           ` M. Edward (Ed) Borasky
2002-01-12  0:29             ` eddantes
2002-01-12  0:34             ` [OT] " Kurt Garloff
2002-01-10 23:50         ` Daniel Phillips
2001-11-12 19:07       ` Timothy D. Witham
2001-11-13  4:53         ` Dan Kegel
2001-11-13 22:00           ` STP for automated GCC testing (was Re: Regression testing of 2.4.x beforerelease?) Bryce Harrington
2001-11-04  7:03 Regression testing of 2.4.x before release? Dan Kegel
2001-11-04  7:15 ` Ted Deppner
2001-11-04 12:04   ` Tahar
2001-11-04 17:27     ` Ted Deppner
2001-11-04 18:41     ` Luigi Genoni

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=3BE581CF.F1AABA25@kegel.com \
    --to=dank@kegel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    --cc=stp@osdlab.org \
    /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).