xfs
[Top] [All Lists]

Re: Snapshot regression test [WAS: re[6]: Summary - Snapshot Effort]

To: Greg Freemyer <freemyer@xxxxxxxxxxxxxxxxx>
Subject: Re: Snapshot regression test [WAS: re[6]: Summary - Snapshot Effort]
From: Steve Lord <lord@xxxxxxx>
Date: 27 Aug 2002 14:13:02 -0500
Cc: Nathan Scott <nathans@xxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <20020827190552.VHDK10702.imf26bis.bellsouth.net@TAZ2>
References: <20020827190552.VHDK10702.imf26bis.bellsouth.net@TAZ2>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Tue, 2002-08-27 at 14:04, Greg Freemyer wrote:
> 
> Nathan,
> 
> I have the very basics of a new test almost working.  I'm assuming it will be 
> 068.
> 
> One big problem I have is that I start a background infinite loop of dd's to 
> generate some i/o load.
> 
> i.e.
> while true; do
>      dd if=/scratch/dummy of=/scratch/junk bs=64k >/dev/null 2>&1
>      rm /scratch/junk
>      sync
> done >/dev/null 2>&1 &
> 
> At the end of the script I kill this off.  Unfortunately, when it dies the 
> parent shell is notifying the user with output like:
> 
> > 068: line 127:  3956 Killed                  while true; do
> >     dd if=/scratch/dummy of=/scratch/junk bs=64k >/dev/null 2>&1; rm 
> > /scratch/junk; sync;
> > done >/dev/null 2>&1
> 
> in my 068.out file.  Since this has pids in the output, I always get a 
> failure message.
> 
> Is there a way to say that output should not be compared, or do you know some 
> shell trick to avoid having this output generated.
> 
> As you can see above, I tried sending stdout and stderr for the subshell to 
> /dev/null, but that did not help.
> 

If you look at some of the other tests, they use awk and sed to process
output to strip variable components like this from the output before
comparison.

Steve


-- 

Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email: lord@xxxxxxx


<Prev in Thread] Current Thread [Next in Thread>