From: Johannes Thumshirn <jthumshirn@suse.de>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
Bart Van Assche <bvanassche@acm.org>,
"Theodore Y. Ts'o" <tytso@mit.edu>
Cc: "lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] improving storage testing
Date: Fri, 15 Feb 2019 08:52:57 +0100 [thread overview]
Message-ID: <d65a562b-b7ef-6342-8cc6-e5ef42c503f3@suse.de> (raw)
In-Reply-To: <BYAPR04MB4502D20C28D486AB49CFAE0A86600@BYAPR04MB4502.namprd04.prod.outlook.com>
On 15/02/2019 03:52, Chaitanya Kulkarni wrote:
> Hi, Bart
>
> In this way, we may end up modifying probably most of the common tools,
> which in long run can create a bunch of the code for the tests. If everyone
> (test contributors and tools maintainers) agrees to have such a "test" mode
> to all the tools, we can go for this approach.
I think going the path similar to xfstests and adding filter functions
to normalize the output in blktests is way less of a hassle than
changing every possible tool we might want to use to have a "test" mode.
Just my two cents,
Johannes
--
Johannes Thumshirn SUSE Labs Filesystems
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2019-02-15 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 18:07 [LSF/MM TOPIC] improving storage testing Theodore Y. Ts'o
2019-02-14 7:37 ` Chaitanya Kulkarni
2019-02-14 10:55 ` Johannes Thumshirn
2019-02-14 16:21 ` David Sterba
2019-02-14 23:26 ` Bart Van Assche
2019-02-15 2:52 ` Chaitanya Kulkarni
2019-02-15 7:52 ` Johannes Thumshirn [this message]
2019-02-14 12:10 ` Lukas Czerner
2019-02-14 21:28 ` Omar Sandoval
2019-02-14 21:56 ` Omar Sandoval
2019-02-15 3:02 ` Theodore Y. Ts'o
2019-02-15 17:32 ` Keith Busch
2019-02-20 1:33 ` Chaitanya Kulkarni
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=d65a562b-b7ef-6342-8cc6-e5ef42c503f3@suse.de \
--to=jthumshirn@suse.de \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=bvanassche@acm.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=tytso@mit.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;
as well as URLs for NNTP newsgroup(s).