From: "Theodore Ts'o" <tytso@mit.edu>
To: fstests@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>
Subject: [PATCH] test-appliance: exclude generic/382 from the ext3 configuration
Date: Mon, 11 Dec 2017 17:36:14 -0500 [thread overview]
Message-ID: <20171211223614.21052-1-tytso@mit.edu> (raw)
The generic/382 test fails on ext3 configuration because the quota
report, which includs the number of blocks used after writing a 30 meg
file, is in the golden output. Unfortunately this doesn't take into
account the indirect blocks which are needed when we are in ext3 mode
and the extents feature is disabled.
It's not clear whether this should be considered a test bug or not,
but at least for now, suppress this test in the ext3 configuration for
{kvm,gce,android}-xfstests.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
---
kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/ext3.exclude | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/ext3.exclude b/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/ext3.exclude
index f78524f..c77c75f 100644
--- a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/ext3.exclude
+++ b/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/ext3.exclude
@@ -1,3 +1,8 @@
# This takes a *long* time and doesn't add much value to run on all
# configurations. So we're going to be selective where we run it.
generic/027
+
+# The generic/382 test fails on ext3 because the indirect blocks
+# are included in the quota report, and so the resulting quota
+# report output is different from what is expected in the 382.out file
+generic/382
--
2.11.0.rc0.7.gbe5a750
reply other threads:[~2017-12-11 22:36 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=20171211223614.21052-1-tytso@mit.edu \
--to=tytso@mit.edu \
--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 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.