From: Dave Chinner <david@fromorbit.com>
To: jeffm@suse.com
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 7/7] check: move test exclusion handling to _prepare_test_list
Date: Tue, 22 Jan 2019 10:09:19 +1100 [thread overview]
Message-ID: <20190121230919.GI4205@dastard> (raw)
In-Reply-To: <20190121163316.20616-7-jeffm@suse.com>
On Mon, Jan 21, 2019 at 11:33:16AM -0500, jeffm@suse.com wrote:
> From: Jeff Mahoney <jeffm@suse.com>
>
> In order to simplify combining excluded tests specified on the command
> line vs specified via config files,
You mean defining excludes in configs/<hostname>.config files,
right? i.e. in config sections?
But the section code only calls _prepare_test_list if the test dev
is recreated by each section, right? So you can't really change the
expunge list from the config files without forcing a test dev
reformat, right?
> it makes sense to push the handling
> into _prepare_test_list. This means we start with a fresh $tmp.xlist
> and rebuild it each time _prepare_test_list is called.
The patch does more than that, right?
> Signed-off-by: Jeff Mahoney <jeffm@suse.com>
> ---
> check | 41 ++++++++++++++++++++++++-----------------
> 1 file changed, 24 insertions(+), 17 deletions(-)
>
> diff --git a/check b/check
> index 77a06b00..17073c4e 100755
> --- a/check
> +++ b/check
> @@ -230,7 +230,28 @@ _prepare_test_list()
> done
> fi
>
> - # Specified groups to exclude
> + :> $tmp.xlist
> +
> + # Per-fstype/generic/shared file of tests to exclude (-X)
> + for xfile in $XGROUP_FILES; do
That adds support for multiple group exclude files (i.e. multiple -X
options), right?
> + for d in $SRC_GROUPS $FSTYP; do
> + [ -f $SRC_DIR/$d/$xfile ] || continue
> + for f in `sed "s/#.*$//" $SRC_DIR/$d/$xfile`; do
> + echo "$d/$f command line" >> $tmp.xlist
> + done
> + done
> + done
> +
> + # External file of tests to exclude (-E)
> + for xfile in $EXCLUDE_FILES; do
> + if [ -f $xfile ]; then
> + sed -e "s/#.*$//" \
> + -e "s;$; file $xfile;" "$xfile" \
And I have no idea what problem this second expression is solving -
it wasn't in the original code that got copied here.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-01-21 23:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 16:33 [PATCH 1/7] btrfs/010: don't run without /sys/fs/btrfs jeffm
2019-01-21 16:33 ` [PATCH 2/7] filter: fix assumed whitespace in _filefrag_filter regex jeffm
2019-01-21 22:51 ` Dave Chinner
2019-01-23 1:38 ` Jeff Mahoney
2019-01-23 4:16 ` Dave Chinner
2019-01-21 16:33 ` [PATCH 3/7] filter: add support for old filefrag -v jeffm
2019-01-21 22:53 ` Dave Chinner
2019-01-23 1:38 ` Jeff Mahoney
2019-01-21 16:33 ` [PATCH 4/7] btrfs: require feature raid56 for raid56 tests jeffm
2019-01-22 22:39 ` Filipe Manana
2019-01-21 16:33 ` [PATCH 5/7] btrfs/023: skip trying to test raid56 without kernel support jeffm
2019-01-22 22:40 ` Filipe Manana
2019-01-21 16:33 ` [PATCH 6/7] btrfs/131: require support for free-space-tree jeffm
2019-01-22 22:41 ` Filipe Manana
2019-01-21 16:33 ` [PATCH 7/7] check: move test exclusion handling to _prepare_test_list jeffm
2019-01-21 23:09 ` Dave Chinner [this message]
2019-01-23 1:59 ` Jeff Mahoney
2019-01-22 22:38 ` [PATCH 1/7] btrfs/010: don't run without /sys/fs/btrfs Filipe Manana
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=20190121230919.GI4205@dastard \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=jeffm@suse.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