From: Hans Reiser <reiser@namesys.com>
To: Valdis.Kletnieks@vt.edu
Cc: "Markus �" <mjt@nysv.org>, "David Masover" <ninja@slaphack.com>,
"Pysiak Satriani" <pysiak.satriani@wp.pl>,
reiserfs-list@namesys.com
Subject: Re: Reiser4 O_DIRECT
Date: Mon, 23 May 2005 10:53:10 -0700 [thread overview]
Message-ID: <42921886.40404@namesys.com> (raw)
In-Reply-To: <200505231653.j4NGrksq017538@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
>On Mon, 23 May 2005 12:52:12 +0300, Markus =?UNKNOWN?Q?T=F6rnqvist?= said:
>
>
>>On Sun, May 22, 2005 at 07:22:51PM -0500, David Masover wrote:
>>
>>
>>>Of course, I've worked on sufficiently few big projects that I'm still
>>>naive enough to believe that unit tests _can_ catch everything, if
>>>they're done right. I'm sure I'll eventually be proven wrong...
>>>
>>>
>>I'm sure a testing professional will happily prove you wrong ;)
>>
>>
>
>It's *never* the testing professional that disproves "unit tests can catch everything".
>
>It's the guy with the creeping-horror Cobol/Python database that finds the stuff
>that unit tests can't catch.. ;)
>
>
>
My favorite for version 3 (we now test for this in v4 testing) was
mozilla truncating files longer rather than shorter. Legal but was not
tested for....
fsx is now the standard file system test tool. It still misses a LOT of
stuff.
Hans
next prev parent reply other threads:[~2005-05-23 17:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 17:53 Reiser4 O_DIRECT Martin Piayda
2005-05-20 8:42 ` Vladimir Saveliev
2005-05-21 21:49 ` Re[2]: " Pysiak Satriani
2005-05-22 7:43 ` Hans Reiser
2005-05-22 17:12 ` mjt
2005-05-22 17:31 ` Hans Reiser
2005-05-22 17:38 ` Martin Piayda
2005-05-26 19:25 ` evilninja
2005-05-22 22:47 ` Re[2]: " Valdis.Kletnieks
2005-05-23 0:22 ` David Masover
2005-05-23 1:04 ` Valdis.Kletnieks
2005-05-23 9:52 ` mjt
2005-05-23 16:53 ` Valdis.Kletnieks
2005-05-23 17:53 ` Hans Reiser [this message]
2005-05-24 21:35 ` David Masover
2005-05-24 21:55 ` Valdis.Kletnieks
2005-05-24 23:28 ` David Masover
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=42921886.40404@namesys.com \
--to=reiser@namesys.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=mjt@nysv.org \
--cc=ninja@slaphack.com \
--cc=pysiak.satriani@wp.pl \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.