From: Luis Chamberlain <mcgrof@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Zorro Lang <zlang@redhat.com>,
Amir Goldstein <amir73il@gmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-block <linux-block@vger.kernel.org>,
pankydev8@gmail.com, Theodore Tso <tytso@mit.edu>,
Josef Bacik <josef@toxicpanda.com>,
jmeneghi@redhat.com, Jan Kara <jack@suse.cz>,
Davidlohr Bueso <dave@stgolabs.net>,
Dan Williams <dan.j.williams@intel.com>, Jake Edge <jake@lwn.net>,
Klaus Jensen <its@irrelevant.dk>,
fstests <fstests@vger.kernel.org>
Subject: Re: [RFC: kdevops] Standardizing on failure rate nomenclature for expunges
Date: Fri, 1 Jul 2022 16:36:29 -0700 [thread overview]
Message-ID: <Yr+E/SvxeSGBbPq1@bombadil.infradead.org> (raw)
In-Reply-To: <YoZq7/lr8hvcs9T3@casper.infradead.org>
On Thu, May 19, 2022 at 05:06:07PM +0100, Matthew Wilcox wrote:
> Right, but that's the personal perspective of an expert tester. I don't
> particularly want to build that expertise myself; I want to write patches
> which touch dozens of filesystems, and I want to be able to smoke-test
> those patches. Maybe xfstests or kdevops doesn't want to solve that
> problem,
kdevop's goals are aligned to enable that. However at this point
in time there is no agreement to share expunges and so we just
carry tons of them per kernel / distro for those that *did* have
time to run them for the environment used and share them.
Today there are baselines for stable and linus' kernel for some
filesystems, but these are on a best effort basis as this takes
system resources and someone's time. The results are tracked in:
workflows/fstests/expunges/
With time now that there is at least a rig to do this for stable
and upstream this should expand to be more up to date. There is
also a shared repo which enables folks to share results there.
Luis
next prev parent reply other threads:[~2022-07-01 23:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 3:07 [RFC: kdevops] Standardizing on failure rate nomenclature for expunges Luis Chamberlain
2022-05-19 6:36 ` Amir Goldstein
2022-05-19 7:58 ` Dave Chinner
2022-05-19 9:20 ` Amir Goldstein
2022-05-19 15:36 ` Josef Bacik
2022-05-19 16:18 ` Zorro Lang
2022-05-19 11:24 ` Zorro Lang
2022-05-19 14:18 ` Theodore Ts'o
2022-05-19 15:10 ` Zorro Lang
2022-05-19 14:58 ` Matthew Wilcox
2022-05-19 15:44 ` Zorro Lang
2022-05-19 16:06 ` Matthew Wilcox
2022-05-19 16:54 ` Zorro Lang
2022-07-01 23:36 ` Luis Chamberlain [this message]
2022-07-02 17:01 ` Theodore Ts'o
2022-07-07 21:36 ` Luis Chamberlain
2022-07-02 21:48 ` Bart Van Assche
2022-07-03 5:56 ` Amir Goldstein
2022-07-03 13:15 ` Theodore Ts'o
2022-07-03 14:22 ` Amir Goldstein
2022-07-03 16:30 ` Theodore Ts'o
2022-07-04 3:25 ` Dave Chinner
2022-07-04 7:58 ` Amir Goldstein
2022-07-05 2:29 ` Theodore Ts'o
2022-07-05 3:11 ` Dave Chinner
2022-07-06 10:11 ` Amir Goldstein
2022-07-06 14:29 ` Theodore Ts'o
2022-07-06 16:35 ` Amir Goldstein
2022-07-03 13:32 ` Theodore Ts'o
2022-07-03 14:54 ` Bart Van Assche
2022-07-07 21:16 ` Luis Chamberlain
2022-07-07 21:06 ` Luis Chamberlain
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=Yr+E/SvxeSGBbPq1@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=amir73il@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=fstests@vger.kernel.org \
--cc=its@irrelevant.dk \
--cc=jack@suse.cz \
--cc=jake@lwn.net \
--cc=jmeneghi@redhat.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pankydev8@gmail.com \
--cc=tytso@mit.edu \
--cc=willy@infradead.org \
--cc=zlang@redhat.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 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).