From: Eryu Guan <eguan@redhat.com>
To: fstests@vger.kernel.org
Cc: Eryu Guan <eguan@redhat.com>
Subject: [PATCH] xfs/167: remove duplicated _require_fs_space
Date: Thu, 17 Sep 2015 22:34:00 +0800 [thread overview]
Message-ID: <1442500440-1328-1-git-send-email-eguan@redhat.com> (raw)
Seems the same patch was applied twice,
6f55bbd xfs/167: need at least 10GB of scratch space to run
b50473c xfs/167: need at least 10GB of scratch space to run
and there're two _require_fs_space calls in the test, remove one.
Signed-off-by: Eryu Guan <eguan@redhat.com>
---
tests/xfs/167 | 6 ------
1 file changed, 6 deletions(-)
diff --git a/tests/xfs/167 b/tests/xfs/167
index 499cc1f..875bd31 100755
--- a/tests/xfs/167
+++ b/tests/xfs/167
@@ -68,12 +68,6 @@ _scratch_mount
# errors.
_require_fs_space $SCRATCH_MNT 10485760
-# fast devices can consume disk space at a rate of 1GB every 5s via the
-# background workload. With 50 test loops, at 1 second per loop, that means we
-# need at least 10GB of disk space to ensure this test will not fail with ENOSPC
-# errors.
-_require_fs_space $SCRATCH_MNT 10485760
-
TEST_FILE=$SCRATCH_MNT/test_file
TEST_PROG=$here/src/unwritten_sync
LOOPS=50
--
2.4.3
reply other threads:[~2015-09-17 14:34 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=1442500440-1328-1-git-send-email-eguan@redhat.com \
--to=eguan@redhat.com \
--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