From: fdmanana@kernel.org
To: fstests@vger.kernel.org
Subject: [PATCH 1/2] btrfs: fix classification of a couple btrfs tests
Date: Sat, 27 Oct 2018 09:48:38 +0100 [thread overview]
Message-ID: <20181027084838.1903-1-fdmanana@kernel.org> (raw)
From: Filipe Manana <fdmanana@suse.com>
Test btrfs/108 does not test collapse, in fact btrfs does not even support
the fallocate collapse operation, so remove it.
Test btrfs/159 does not test collapse either, it tests hole punching, so
replace the collapse group with the punch group.
Signed-off-by: Filipe Manana <fdmanana@suse.com>
---
tests/btrfs/group | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/btrfs/group b/tests/btrfs/group
index 45782565..3ea84b1c 100644
--- a/tests/btrfs/group
+++ b/tests/btrfs/group
@@ -110,7 +110,7 @@
105 auto quick send
106 auto quick clone compress
107 auto quick prealloc
-108 auto quick send clone punch collapse
+108 auto quick send clone punch
109 auto quick send clone compress
110 auto quick send
111 auto quick send
@@ -161,7 +161,7 @@
156 auto quick trim
157 auto quick raid
158 auto quick raid scrub
-159 auto quick collapse
+159 auto quick punch
160 auto quick
161 auto quick volume
162 auto quick volume
--
2.11.0
reply other threads:[~2018-10-27 17:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20181027084838.1903-1-fdmanana@kernel.org \
--to=fdmanana@kernel.org \
--cc=fstests@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