From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Craig Thomas <craiger@osdl.org>
Cc: Scott Robert Ladd <coyote@coyotegulch.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Testing: What do you want?
Date: Tue, 25 Mar 2003 01:16:27 +0100 [thread overview]
Message-ID: <20030325001627.GC14469@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1048547186.495.43.camel@bullpen.pdx.osdl.net>
On Mon, 24 March 2003 15:06:26 -0800, Craig Thomas wrote:
>
> OSDL has a set of stress tests that are run on new kernels as they
> become available. However, the architectures tested are limited
> (compared with the variety that can be found in the world). There
> are enough testers in the community to collectively test for
> correctness of the kernel. Test suites such as LTP and LSB help
> in this regard.
>
> On Mon, 2003-03-24 at 09:01, Alan Cox wrote:
> >
> > One of the best things people can do is just use it. OSDL and others run
> > stress tests but often its users configurations that find bugs not
> > stress and coverage runs.
And another thing I have found to be good at finding bugs is a sick
mind. If you intend to crash a system and do just about anything a
normal user wouldn't, you will stress all the code paths that are
usually not tested.
Jörn
--
To recognize individual spam features you have to try to get into the
mind of the spammer, and frankly I want to spend as little time inside
the minds of spammers as possible.
-- Paul Graham
next prev parent reply other threads:[~2003-03-25 0:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 14:46 Scott Robert Ladd
2003-03-24 15:39 ` Jan-Benedict Glaw
2003-03-24 17:30 ` Scott Robert Ladd
2003-03-25 0:04 ` Rob Radez
2003-03-25 17:50 ` Craig Thomas
2003-03-24 17:01 ` Alan Cox
2003-03-24 23:06 ` Craig Thomas
2003-03-25 0:16 ` Jörn Engel [this message]
2003-03-25 14:18 ` Scott Robert Ladd
2003-03-25 14:18 ` Scott Robert Ladd
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=20030325001627.GC14469@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=coyote@coyotegulch.com \
--cc=craiger@osdl.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®