From: "Theodore Ts'o" <tytso@mit.edu>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
"Darrick J. Wong" <djwong@kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-block <linux-block@vger.kernel.org>,
Pankaj Raghav <pankydev8@gmail.com>,
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>, Zorro Lang <zlang@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
Dave Chinner <david@fromorbit.com>
Subject: Re: [RFC: kdevops] Standardizing on failure rate nomenclature for expunges
Date: Sun, 3 Jul 2022 12:30:16 -0400 [thread overview]
Message-ID: <YsHEGElna2Ae2V83@mit.edu> (raw)
In-Reply-To: <CAOQ4uxhEaVjk6rEnsnjWOKs+dygioXk-9h-WJjBzkJfe8U9eMQ@mail.gmail.com>
On Sun, Jul 03, 2022 at 05:22:17PM +0300, Amir Goldstein wrote:
>
> To be clear, when I wrote deterministic, what I meant was deterministic
> results empirically, in the same sense that Bart meant - a test should
> always pass.
Well all of the tests in the auto group pass at 100% of the time for
the ext4/4k and xfs/4k groups. (Well, at least if use the HDD and SSD
as the storage device. If you are using eMMC flash, or Luis's loop
device config, there would be more failures.)
But if we're talking about btrfs/4k, f2fs/4k, xfs/realtime,
xfs/realtime_28k/logdev, ext4/bigalloc, etc. there would be a *lot* of
tests that would need to be removed from the auto group.
So what "non-determinsitic tests" should we remove from the auto
group? For what file systems, file system configs, and storage
devices? What would you propose?
Remember, Matthew wants something that he can use to test "dozens" of
file systems that he's touching for the folio patches. If we have to
remove all of the tests that fail if you are using nfs, vfat, hfs,
msdos, etc., then the auto group would be pretty anemic. Let's not do
that.
If you want a "always pass" group, we could do that, but let's not
call that the "auto" group, please.
- Ted
next prev parent reply other threads:[~2022-07-03 16:30 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
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 [this message]
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=YsHEGElna2Ae2V83@mit.edu \
--to=tytso@mit.edu \
--cc=amir73il@gmail.com \
--cc=bvanassche@acm.org \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--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=mcgrof@kernel.org \
--cc=pankydev8@gmail.com \
--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).