From: Pavel Reichl <preichl@redhat.com>
To: fstests@vger.kernel.org
Subject: [PATCH 2/4] g/299: speed up the test
Date: Thu, 22 Sep 2022 15:48:20 +0200 [thread overview]
Message-ID: <20220922134822.1020119-2-preichl@redhat.com> (raw)
In-Reply-To: <20220922134822.1020119-1-preichl@redhat.com>
Move the _require_xfs_io_command "falloc" above the
potencially 'expensive' function _get_max_file_size
Signed-off-by: Pavel Reichl <preichl@redhat.com>
---
tests/generic/299 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/generic/299 b/tests/generic/299
index 8e1a112c..1bb371a3 100755
--- a/tests/generic/299
+++ b/tests/generic/299
@@ -24,6 +24,7 @@ _require_scratch
_require_odirect
_require_aio
_require_block_device $SCRATCH_DEV
+_require_xfs_io_command "falloc"
NUM_JOBS=$((4*LOAD_FACTOR))
BLK_DEV_SIZE=`blockdev --getsz $SCRATCH_DEV`
@@ -96,7 +97,6 @@ filename=buffered-aio-verifier
EOF
_require_fio $fio_config
-_require_xfs_io_command "falloc"
_scratch_mkfs >> $seqres.full 2>&1
_scratch_mount
--
2.37.3
next prev parent reply other threads:[~2022-09-22 13:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 13:48 [PATCH 1/4] common: Fix file leak in _get_max_file_size Pavel Reichl
2022-09-22 13:48 ` Pavel Reichl [this message]
2022-09-22 15:16 ` [PATCH 2/4] g/299: speed up the test Zorro Lang
2022-09-22 13:48 ` [PATCH 3/4] generic: cleanup test files Pavel Reichl
2022-09-22 14:36 ` Zorro Lang
[not found] ` <91ec6d59-5014-2e3e-8e80-aac162b8ffc1@redhat.com>
2022-09-22 15:08 ` Zorro Lang
2022-09-22 17:05 ` Pavel Reichl
2022-09-22 17:58 ` Zorro Lang
2022-09-22 13:48 ` [PATCH 4/4] g/394: clean up " Pavel Reichl
2022-09-22 15:04 ` Zorro Lang
2022-09-22 14:46 ` [PATCH 1/4] common: Fix file leak in _get_max_file_size Zorro Lang
2022-09-22 14:51 ` Pavel Reichl
2022-09-23 3:31 ` Eric Biggers
2022-09-23 5:04 ` Zorro Lang
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=20220922134822.1020119-2-preichl@redhat.com \
--to=preichl@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 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.