From: Nathan Straz <nstraz@sgi.com>
To: Khyron <khyron@khyron.com>
Cc: LKML - Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Test Project <ltp-list@lists.sourceforge.net>
Subject: Re: Kernel test suites (was Re: Coding style - a non-issue)
Date: Tue, 11 Dec 2001 11:51:02 -0600 [thread overview]
Message-ID: <20011211115102.A1637@sgi.com> (raw)
In-Reply-To: <Pine.BSF.4.33.0112032202420.98724-100000@four.malevolentminds.com>
In-Reply-To: <Pine.BSF.4.33.0112032202420.98724-100000@four.malevolentminds.com>
On Mon, Dec 03, 2001 at 10:28:44PM +0000, Khyron wrote:
> I would be interested in seeing this test suite as well.
>
> Also, if anyone with any background on the subject can
> chime in on the RH test suite and how the Linux Test Project
> compare/overlap/differ, that would be good to know too.
The bulk of LTP is regression tests. There are a number of stress tests
in LTP, but not the ones in the RH test suite (if the one below is
correct). Also, LTP doesn't use CTCS, but its own test driver.
> Alan Cox previously replied to Stanislav Meduna saying:
> > Is the test suite (or at least part of it) public, or is it
> > considered to be a trade-secret of Red Hat? I see there
> > is a "Red Hat Ready Test Suite" - is this a part of it?
>
> The main Red Hat test suite is a version of Cerberus (originally from VA
> and much extended), its all free software and its available somewhere
> although I don't have the URL to hand, Arjan ?
I'm not sure if this is it or not, but this is the package I was once
pointed to.
http://people.redhat.com/bmatthews/cerberus/stress-kernel-*
--
Nate Straz nstraz@sgi.com
sgi, inc http://www.sgi.com/
Linux Test Project http://ltp.sf.net/
prev parent reply other threads:[~2001-12-11 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 22:28 Kernel test suites (was Re: Coding style - a non-issue) Khyron
2001-12-11 17:51 ` Nathan Straz [this message]
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=20011211115102.A1637@sgi.com \
--to=nstraz@sgi.com \
--cc=khyron@khyron.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
/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