From: Hans Reiser <reiser@namesys.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Martin Dalecki <dalecki@evision-ventures.com>,
Rik van Riel <riel@conectiva.com.br>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: PROBLEM: Kernel Panic on 2.5.6 and 2.5.7-pre1 boot [PATCH] and discussion of Linux testing procedures
Date: Wed, 13 Mar 2002 21:46:11 +0300 [thread overview]
Message-ID: <3C8F9E73.6000200@namesys.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0203130903470.22930-100000@weyl.math.psu.edu>
Alexander Viro wrote:
>
>
>Proposal is a bit naive, though - in most of the cases fuckups merrily
>pass original testing.
>
>
>
No, I think we catch 70-85%. Namesys internal bad patches frequently
pass original testing of patch author and are caught by professional
tester whose specialty is testing reiserfs patches. You just haven't
seen these bad patches, so you don't realize how effective the catching
is.;-) There have been a lot of catches.;-) It is not simply a matter
of skill in testing though: you need a second person to test it in the
way that the author did not think to test it (e.g. by booting to the
right kernel, everyone on this list has made that benchmarking/testing
error a few times, yes....;-) ).
Hans
prev parent reply other threads:[~2002-03-13 18:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 10:02 PROBLEM: Kernel Panic on 2.5.6 and 2.5.7-pre1 boot [PATCH] and discussion of Linux testing procedures Hans Reiser
2002-03-13 13:50 ` Rik van Riel
2002-03-13 13:57 ` Martin Dalecki
2002-03-13 14:09 ` Alexander Viro
2002-03-13 14:18 ` Martin Dalecki
2002-03-13 17:03 ` [reiserfs-list] " Valdis.Kletnieks
2002-03-13 17:44 ` Alexander Viro
2002-03-13 18:46 ` Hans Reiser [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=3C8F9E73.6000200@namesys.com \
--to=reiser@namesys.com \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=riel@conectiva.com.br \
--cc=viro@math.psu.edu \
/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