From: Eric Whitney <enwlinux@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu
Subject: [PATCH] xfstests-bld: add exclude file for data_journal_noleak tests
Date: Tue, 12 Jan 2016 14:52:48 -0500 [thread overview]
Message-ID: <20160112195248.GA1941@localhost.localdomain> (raw)
Duplicate the contents of the data_journal exclude file for the
data_journal_noleak test case. This will prevent failure reports from
tests already known to exercise unsupported online defrag functionality.
Add an explanatory comment to both exclude files for future reference.
Signed-off-by: Eric Whitney <enwlinux@gmail.com>
---
kvm-xfstests/test-appliance/files/root/conf/data_journal.exclude | 1 +
.../test-appliance/files/root/conf/data_journal_noleak.exclude | 7 +++++++
2 files changed, 8 insertions(+)
create mode 100644 kvm-xfstests/test-appliance/files/root/conf/data_journal_noleak.exclude
diff --git a/kvm-xfstests/test-appliance/files/root/conf/data_journal.exclude b/kvm-xfstests/test-appliance/files/root/conf/data_journal.exclude
index b925016..7190c8c 100644
--- a/kvm-xfstests/test-appliance/files/root/conf/data_journal.exclude
+++ b/kvm-xfstests/test-appliance/files/root/conf/data_journal.exclude
@@ -1,3 +1,4 @@
+# data_journal does not support on-line defrag
ext4/301
ext4/302
ext4/303
diff --git a/kvm-xfstests/test-appliance/files/root/conf/data_journal_noleak.exclude b/kvm-xfstests/test-appliance/files/root/conf/data_journal_noleak.exclude
new file mode 100644
index 0000000..7190c8c
--- /dev/null
+++ b/kvm-xfstests/test-appliance/files/root/conf/data_journal_noleak.exclude
@@ -0,0 +1,7 @@
+# data_journal does not support on-line defrag
+ext4/301
+ext4/302
+ext4/303
+ext4/304
+ext4/307
+ext4/308
--
2.1.4
next reply other threads:[~2016-01-12 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 19:52 Eric Whitney [this message]
2016-01-12 20:35 ` [PATCH] xfstests-bld: add exclude file for data_journal_noleak tests Dave Chinner
2016-01-13 16:55 ` Theodore Ts'o
2016-01-18 22:16 ` Dave Chinner
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=20160112195248.GA1941@localhost.localdomain \
--to=enwlinux@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.