public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Czerner <lczerner@redhat.com>
To: xfs@oss.sgi.com
Cc: Lukas Czerner <lczerner@redhat.com>
Subject: [PATCH 02/10] xfstests: Export all important variables in common/config
Date: Wed, 10 Jul 2013 16:00:31 +0200	[thread overview]
Message-ID: <1373464839-31535-3-git-send-email-lczerner@redhat.com> (raw)
In-Reply-To: <1373464839-31535-1-git-send-email-lczerner@redhat.com>

Currently we do not export some of the important variables in
common/config. Fix this.

Signed-off-by: Lukas Czerner <lczerner@redhat.com>
---
 common/config | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/common/config b/common/config
index 67c1498..1679acf 100644
--- a/common/config
+++ b/common/config
@@ -56,19 +56,19 @@ export LANG=C
 [ -d /usr/freeware/bin ] && PATH=$PATH:/usr/freeware/bin
 PATH=".:$PATH"
 
-HOST=`hostname -s`
-HOSTOS=`uname -s`
-[ "$HOSTOS" = "IRIX64" ] && HOSTOS="IRIX"
+export HOST=`hostname -s`
+export HOSTOS=`uname -s`
+[ "$HOSTOS" = "IRIX64" ] && export HOSTOS="IRIX"
 
-MODULAR=0               # using XFS as a module or not
-BOOT="/boot"            # install target for kernels
+export MODULAR=0               # using XFS as a module or not
+export BOOT="/boot"            # install target for kernels
 export EXTRA=${EXTRA:=xfs-qa}
 
 # general parameters (mainly for auto-qa)
-SOAK_PROC=3             # -p option to fsstress
-SOAK_STRESS=10000       # -n option to fsstress
-SOAK_PASSES=-1          # count of repetitions of fsstress (while soaking)
-EMAIL=root@localhost    # where auto-qa will send its status messages
+export SOAK_PROC=3             # -p option to fsstress
+export SOAK_STRESS=10000       # -n option to fsstress
+export SOAK_PASSES=-1          # count of repetitions of fsstress (while soaking)
+export EMAIL=root@localhost    # where auto-qa will send its status messages
 export HOST_OPTIONS=${HOST_OPTIONS:=local.config}
 export CHECK_OPTIONS=${CHECK_OPTIONS:="-g auto"}
 export BENCH_PASSES=${BENCH_PASSES:=5}
-- 
1.8.3.1

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

  parent reply	other threads:[~2013-07-10 14:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10 14:00 [RFC][PATCH 00/10] xfstests: Add support for config section Lukas Czerner
2013-07-10 14:00 ` [PATCH 01/10] xfstests: Run all tests when nothing is specified Lukas Czerner
2013-07-10 14:00 ` Lukas Czerner [this message]
2013-07-10 14:00 ` [PATCH 03/10] xfstests: Refactor code for obtaining test list Lukas Czerner
2013-07-10 14:00 ` [PATCH 04/10] xfstests: Allow to recheck options in common/rc Lukas Czerner
2013-07-10 14:00 ` [PATCH 05/10] xfstests: Allow to re-read configuration Lukas Czerner
2013-07-10 14:00 ` [PATCH 06/10] xfstests: Allow to specify RESULT_BASE directory Lukas Czerner
2013-07-10 14:00 ` [PATCH 07/10] xfstests: Prepare for config section Lukas Czerner
2013-07-10 14:00 ` [PATCH 08/10] xfstests: Add support for sections in config file Lukas Czerner
2013-07-10 14:00 ` [PATCH 09/10] xfstests: Allow to recreate TEST_DEV Lukas Czerner
2013-07-10 14:00 ` [PATCH 10/10] xfstests: Remount file system if MOUNT_OPTIONS changed Lukas Czerner

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=1373464839-31535-3-git-send-email-lczerner@redhat.com \
    --to=lczerner@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox