[Top] [All Lists]

Re: [PATCH] xfstest: fix filtering in 206 for ftype and projid32bit

To: Mark Tinguely <tinguely@xxxxxxx>
Subject: Re: [PATCH] xfstest: fix filtering in 206 for ftype and projid32bit
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Sun, 27 Oct 2013 20:11:21 +1100
Cc: XFS Community <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <5269A35F.5080500@xxxxxxx>
References: <20131024215652.413619467@xxxxxxx> <20131024221136.GZ2797@dastard> <5269A35F.5080500@xxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Thu, Oct 24, 2013 at 05:46:55PM -0500, Mark Tinguely wrote:
> On 10/24/13 17:11, Dave Chinner wrote:
> >On Thu, Oct 24, 2013 at 04:56:42PM -0500, Mark Tinguely wrote:
> >>xfs/206 displays the output for mkfs.xfs, xfs_growfs and xfs_info.
> >>Change the filtering to hide the new output for the field type
> >>feature.
> >>
> >>While cleaning up the ftype output, also clean up the projid32bit
> >>output in xfs_growfs and xfs_info.
> >
> >What about the _filter_mkfs function that other tests use?
> >
> >Cheers,
> >
> >Dave.
> From what I can tell, it does not need changing.

We really should be exporting the values as shell variables to
stderr for any test that wants to use them. We don't need to output
them to stdout at this point (as that will break all the golden
images), but all the mkfs config values should be accessible from
the filter.

i.e. _filter_mkfs is infrastructure and when new things are added,
the infrastructure needs to be updated as well. IOWs, this should
work after you've added support for ftype to xfstests:

_scratch_mkfs | _mkfs_filter 2> $tmp.mkfs > /dev/null
. $tmp.mkfs

if [ $nftype -eq 1 ]; then


Dave Chinner

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