All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH] xfstests: skip fsr tests if xfs_fsr utils not found
Date: Sun, 19 Apr 2009 16:50:59 -0500	[thread overview]
Message-ID: <49EB9CC3.1000305@sandeen.net> (raw)
In-Reply-To: <49EB8F90.20705@sandeen.net>

Similar to the xfsdump-related patch; gracefully fail
if no xfs_fsr is found.

I'll probably send another for the acl & attr userspace,
it's actually not always installed on minimal boxes.

Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
---

diff --git a/042 b/042
index 7c2bcac..6628040 100755
--- a/042
+++ b/042
@@ -37,6 +37,8 @@ _supported_os IRIX Linux
 
 _require_scratch
 
+[ "$XFS_FSR_PROG" = "" ] && _notrun "xfs_fsr not found"
+
 _cull_files()
 {
     perl -e "\$manifest=\"$tmp.manifest\";" -e '
diff --git a/111 b/111
index 060c0bc..3ce4ee1 100755
--- a/111
+++ b/111
@@ -27,6 +27,8 @@ _supported_fs xfs
 _supported_os Linux
 _require_scratch
 
+[ "$XFS_FSR_PROG" = "" ] && _notrun "xfs_fsr not found"
+
 # real QA test starts here
 umount $SCRATCH_DEV 2>/dev/null
 MKFS_OPTIONS="-bsize=4096"


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2009-04-19 21:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19 20:54 [PATCH] xfstests: skip dump tests if dump utils not found Eric Sandeen
2009-04-19 21:38 ` Christoph Hellwig
2009-04-19 21:43 ` Josef 'Jeff' Sipek
2009-04-19 21:50 ` Eric Sandeen [this message]
2009-04-19 22:14   ` [PATCH] xfstests: skip fsr tests if xfs_fsr " Felix Blyakher
2009-04-21 14:14   ` Christoph Hellwig
2009-04-19 22:13 ` [PATCH] xfstests: skip dump tests if dump " Felix Blyakher

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=49EB9CC3.1000305@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.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 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.