public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Straz <nstraz@sgi.com>
To: Wade Hampton <whampton@staffnet.com>
Cc: nbecker@fred.net, linux-kernel@vger.kernel.org
Subject: Re: regression testing
Date: Thu, 22 Mar 2001 09:56:16 -0600	[thread overview]
Message-ID: <20010322095616.A23245@sgi.com> (raw)
In-Reply-To: <x88zoeeeyh8.fsf@adglinux1.hns.com> <3ABA1680.D1467727@staffnet.com>
In-Reply-To: <3ABA1680.D1467727@staffnet.com>; from whampton@staffnet.com on Thu, Mar 22, 2001 at 10:13:04AM -0500

On Thu, Mar 22, 2001 at 10:13:04AM -0500, Wade Hampton wrote:
> nbecker@fred.net wrote:
> > Hi.  I was wondering if there has been any discussion of kernel
> > regression testing.  Wouldn't it be great if we didn't have to depend
> > on human testers to verify every change didn't break something?
> IMHO, much of the strength of Linux is the very large, extremely 
> diverse population of folks using it, testing it, beating on 
> the latest release, etc.  

The Linux community definately provides the configuration testing that
could never be done in a lab setting.  At least one that most companies
could afford.  

> However, a lab dedicated to testing the linux kernel, properly 
> funded, staffed, and containing the most common hardware and 
> software would be a good idea.  Does anyone have any idea how
> this could be accomplished?  Who could do it?  IBM?  What would
> it cost to setup a reasonable lab?  My guess would be dozens 
> of machines of various architectures, a staff of at least 10,
> several thousand square feet of space, and a good budget....
> Any takers?  

SGI is working on regression testing for Linux.  We have released some
of our tests and utilities under the Linux Test Project.  IMHO, a few
hundred tests aren't enough.  I need to make another big push with the
tests I've ported over the last few months.  

I believe there is some work in the Open Source Development Lab that
some IBMers could comment on.  I don't know if there is a web site
detailing their efforts yet.  

-- 
Nate Straz                                              nstraz@sgi.com
sgi, inc                                           http://www.sgi.com/
Linux Test Project                    http://oss.sgi.com/projects/ltp/

  reply	other threads:[~2001-03-22 15:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22 13:15 regression testing nbecker
2001-03-22 13:39 ` Richard B. Johnson
2001-03-22 13:47   ` nbecker
2001-03-22 14:47   ` Alan Cox
2001-03-22 14:45     ` Richard B. Johnson
2001-03-22 18:18   ` Cort Dougan
2001-03-22 15:13 ` Wade Hampton
2001-03-22 15:56   ` Nathan Straz [this message]
2001-03-22 16:46     ` Nathan Dabney
2001-03-22 16:37 ` Rik van Riel
2001-03-22 18:21   ` Cort Dougan
2001-03-22 18:12 ` Jonathan Morton
2001-03-23 15:00   ` Horst von Brand
2001-03-23 15:29     ` Rik van Riel
2001-03-23 10:11 ` Eric W. Biederman
2001-03-27  7:21   ` Werner Almesberger
  -- strict thread matches above, loose matches on Subject: below --
2001-03-22 18:44 Torrey Hoffman

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=20010322095616.A23245@sgi.com \
    --to=nstraz@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbecker@fred.net \
    --cc=whampton@staffnet.com \
    /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