public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Baihua Lu <lubaihua0331@gmail.com>
To: fstests@vger.kernel.org, guaneryu@gmail.com, darrick.wong@oracle.com
Cc: balu@microsoft.com, Lili.Deng@microsoft.com,
	Baihua Lu <lubaihua0331@gmail.com>
Subject: [PATCH] xfs/191-input-validation:Fix issue that the test takes too long
Date: Wed, 27 Nov 2019 10:41:31 +0000	[thread overview]
Message-ID: <20191127104131.112533-1-lubaihua0331@gmail.com> (raw)

After this test is passed, checking filesystems will execute. Then
xfs_logprint will be failed and xfs_repair will take a long time because
there is not really creating the file system in this test and wipefs
executes before this test. So there is no need checking filesystems.

Signed-off-by: Baihua Lu <lubaihua0331@gmail.com>
---
 tests/xfs/191-input-validation | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/xfs/191-input-validation b/tests/xfs/191-input-validation
index b6658015..db427349 100755
--- a/tests/xfs/191-input-validation
+++ b/tests/xfs/191-input-validation
@@ -31,7 +31,7 @@ _cleanup()
 # Modify as appropriate.
 _supported_fs xfs
 _supported_os Linux
-_require_scratch
+_require_scratch_nocheck
 _require_xfs_mkfs_validation
 
 
-- 
2.17.1


             reply	other threads:[~2019-11-27 10:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 10:41 Baihua Lu [this message]
2019-11-27 16:31 ` [PATCH] xfs/191-input-validation:Fix issue that the test takes too long Darrick J. Wong
  -- strict thread matches above, loose matches on Subject: below --
2019-11-26  5:23 Baihua Lu
2019-11-26 15:36 ` Darrick J. Wong
2019-11-20  8:17 Baihua Lu

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=20191127104131.112533-1-lubaihua0331@gmail.com \
    --to=lubaihua0331@gmail.com \
    --cc=Lili.Deng@microsoft.com \
    --cc=balu@microsoft.com \
    --cc=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=guaneryu@gmail.com \
    /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