From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Theodore Ts'o <tytso@mit.edu>, Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: RFC: don't fail tests when mkfs options collide
Date: Sat, 27 Jul 2024 19:24:48 -0700 [thread overview]
Message-ID: <20240728021016.GF612460@frogsfrogsfrogs> (raw)
In-Reply-To: <20240726171145.GA27555@lst.de>
On Fri, Jul 26, 2024 at 07:11:45PM +0200, Christoph Hellwig wrote:
> On Fri, Jul 26, 2024 at 09:20:14AM -0700, Darrick J. Wong wrote:
> > The big question I have is: for at least the standard -g all runs, does
> > this decrease the number of tests selected?
>
> For a -g auto / -g quick run without any extra options it does not
> change test coverage at all. It only kicks in if you add "problematic"
> mkfs options.
<nod> In that case, I think I'm ok with letting this graduate to
for-next to see what happens :)
Acked-by: Darrick J. Wong <djwong@kernel.org>
--D
prev parent reply other threads:[~2024-07-28 2:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 0:00 RFC: don't fail tests when mkfs options collide Christoph Hellwig
2024-07-23 0:00 ` [PATCH 1/4] common: _notrun if _scratch_mkfs_sized failed Christoph Hellwig
2024-07-23 0:00 ` [PATCH 2/4] common: _notrun if _scratch_mkfs_xfs failed Christoph Hellwig
2024-07-26 17:14 ` Zorro Lang
2024-07-26 18:11 ` Christoph Hellwig
2024-07-28 14:54 ` Zorro Lang
2024-07-29 14:17 ` Christoph Hellwig
2024-07-23 0:00 ` [PATCH 3/4] xfs/432: use _scratch_mkfs_xfs Christoph Hellwig
2024-07-23 0:00 ` [PATCH 4/4] xfs/516: " Christoph Hellwig
2024-07-23 3:50 ` RFC: don't fail tests when mkfs options collide Theodore Ts'o
2024-07-23 13:39 ` Christoph Hellwig
2024-07-23 14:17 ` Theodore Ts'o
2024-07-23 14:20 ` Christoph Hellwig
2024-07-26 16:20 ` Darrick J. Wong
2024-07-26 17:11 ` Christoph Hellwig
2024-07-28 2:24 ` Darrick J. Wong [this message]
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=20240728021016.GF612460@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=zlang@kernel.org \
/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.