From: David Sterba <dsterba@suse.cz>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
lsf-pc@lists.linux-foundation.org, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM TOPIC] improving storage testing
Date: Thu, 14 Feb 2019 17:21:09 +0100 [thread overview]
Message-ID: <20190214162109.GC9874@twin.jikos.cz> (raw)
In-Reply-To: <20190214105507.GA9739@linux-x5ow.site>
On Thu, Feb 14, 2019 at 11:55:07AM +0100, Johannes Thumshirn wrote:
> On Wed, Feb 13, 2019 at 01:07:54PM -0500, Theodore Y. Ts'o wrote:
> > 2) Documenting what are known failures should be for various tests on
> > different file systems and kernel versions. I think we all have our
> > own way of excluding tests which are known to fail. One extreme case
> > is where the test case was added to xfstests (generic/484), but the
> > patch to fix it got hung up because it was somewhat controversial, so
> > it was failing on all file systems.
>
> How about having a wiki page, either in the respective filesystems wiki or a
> common wiki, that show's the list of test that are expected to fail for kernel
> version X?
>
> This is something I'm desperately looking for for brtfs for example.
https://btrfs.wiki.kernel.org/index.php/Development_notes#.28x.29fstests
Feel free to add what you're missing to that page. Though I'm not sure
wiki is the best way to track such information, but it can be a start.
Without people regularly checking that the information is accurate, it
will be obsolete and fallback to own scripts and exclusion lists would
happen.
next prev parent reply other threads:[~2019-02-14 16:19 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 [this message]
2019-02-14 23:26 ` Bart Van Assche
2019-02-15 2:52 ` Chaitanya Kulkarni
2019-02-15 7:52 ` Johannes Thumshirn
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=20190214162109.GC9874@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=jthumshirn@suse.de \
--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).