From: fdmanana@kernel.org
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: [PATCH 0/3] btrfs: fix some test failures with btrfs-progs 5.19 and 6.0
Date: Wed, 9 Nov 2022 11:43:33 +0000 [thread overview]
Message-ID: <cover.1667993961.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
The output of some commands changed with btrfs-progs 5.19 and 6.0, as well
as the --leafsize/-l command line option was removed from mkfs. These make
some tests fail. This patchset changes the tests so that they work with the
new btrfs-progs versions as well as older versions.
Filipe Manana (3):
btrfs/003: fix failure on new btrfs-progs versions
btrfs/053: fix test failure when running with btrfs-progs v6.0+
btrfs: fix failure of tests that use defrag on btrfs-progs v6.0+
tests/btrfs/003 | 5 +++--
tests/btrfs/021 | 4 +++-
tests/btrfs/053 | 4 ++--
tests/btrfs/256 | 4 +++-
4 files changed, 11 insertions(+), 6 deletions(-)
--
2.35.1
next reply other threads:[~2022-11-09 11:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 11:43 fdmanana [this message]
2022-11-09 11:43 ` [PATCH 1/3] btrfs/003: fix failure on new btrfs-progs versions fdmanana
2022-11-09 15:37 ` Zorro Lang
2022-11-09 11:43 ` [PATCH 2/3] btrfs/053: fix test failure when running with btrfs-progs v6.0+ fdmanana
2022-11-09 15:55 ` Zorro Lang
2022-11-09 16:43 ` Filipe Manana
2022-11-09 11:43 ` [PATCH 3/3] btrfs: fix failure of tests that use defrag on " fdmanana
2022-11-09 16:01 ` Zorro Lang
2022-11-09 16:44 ` [PATCH v2 0/3] btrfs: fix some test failures with btrfs-progs 5.19 and 6.0 fdmanana
2022-11-09 16:44 ` [PATCH v2 1/3] btrfs/003: fix failure on new btrfs-progs versions fdmanana
2022-11-14 11:19 ` Qu Wenruo
2022-11-09 16:44 ` [PATCH v2 3/3] btrfs: fix failure of tests that use defrag on btrfs-progs v6.0+ fdmanana
2022-11-14 11:09 ` Qu Wenruo
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=cover.1667993961.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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