From: Kent Overstreet <kent.overstreet@gmail.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-bcachefs@vger.kernel.org
Subject: Re: [PATCH v2 4/4] generic/269: add _check_scratch_fs
Date: Tue, 25 May 2021 21:53:46 -0400 [thread overview]
Message-ID: <YK2qKlYgnfd/eX62@moria.home.lan> (raw)
In-Reply-To: <20210526013418.GK202095@locust>
On Tue, May 25, 2021 at 06:34:18PM -0700, Darrick J. Wong wrote:
> On Tue, May 25, 2021 at 06:19:55PM -0400, Kent Overstreet wrote:
> > This probably should be in every test that uses the scratch device.
>
> Um, it is -- ./check runs fsck on the test and scratch devices if you
> _require_test or _require_scratch'd them (which this test does). What
> weird output did you see?
I could've sworn I had generic/269 pass until I adedd that, but I just rechecked
and it's doing what you describe - my bad, I'll drop this one.
prev parent reply other threads:[~2021-05-26 1:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 22:19 [PATCH 1/4] Improved .gitignore Kent Overstreet
2021-05-25 22:19 ` [PATCH 2/4] Initial bcachefs support Kent Overstreet
2021-05-25 22:19 ` [PATCH 3/4] generic/{455,457,482}: make dmlogwrites tests work on bcachefs Kent Overstreet
2021-05-25 22:19 ` [PATCH 4/4] generic/269: add _check_scratch_fs Kent Overstreet
2021-05-25 22:19 ` [PATCH v2 1/4] Improved .gitignore Kent Overstreet
2021-05-25 22:19 ` [PATCH v2 2/4] Initial bcachefs support Kent Overstreet
2021-05-25 22:19 ` [PATCH v2 3/4] generic/{455,457,482}: make dmlogwrites tests work on bcachefs Kent Overstreet
2021-05-30 13:18 ` Eryu Guan
2021-06-01 18:50 ` Kent Overstreet
2021-05-25 22:19 ` [PATCH v2 4/4] generic/269: add _check_scratch_fs Kent Overstreet
2021-05-26 1:34 ` Darrick J. Wong
2021-05-26 1:53 ` Kent Overstreet [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=YK2qKlYgnfd/eX62@moria.home.lan \
--to=kent.overstreet@gmail.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.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 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).