All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Zorro Lang <zlang@kernel.org>
Cc: fstests@vger.kernel.org
Subject: Re: [ANNOUNCE] fstests: for-next branch updated to v2024.07.14
Date: Mon, 15 Jul 2024 11:44:54 -0400	[thread overview]
Message-ID: <20240715154454.GB70013@mit.edu> (raw)
In-Reply-To: <64ec6187145dfd111f22f1ae151ae538@kernel.org>

On Sun, Jul 14, 2024 at 10:00:37PM +0800, Zorro Lang wrote:
> 2. Most of cases have removed '_supported_fs' line. From now on, if you don't
>    need a specific white or black fs list for a case, don't need _supported_fs
>    line.

A side effect of this change was that it triggered a failure in my GCE
test-appliance's regression test suite.  That's because one of the
things the regression tests run is: 

	gce-xfstests -c ext4/4k,btrfs/4k btrfs/001 generic/001 generic/002

and previously, when testing the ext4/4k configuration, btrfs/001
would be skipped due to its "_supported_fs btrfs" line.  Now, the test
is actually run, and it fails (unsurprisingly).

I'm going to work around this in my test appliance, so I'm not asking
that the change be reverted, but I thought I would point out that this
does result in a behavioural change in some corner cases.

       	    		       	       	      - Ted

commit 71b003b9ad0a0f0e4bf91619702addd0bb552f7d
Author: Theodore Ts'o <tytso@mit.edu>
Date:   Mon Jul 15 11:34:30 2024 -0400

    test-appliance: exclude tests that are not supported for the file system type
    
    This is needed due to upstream xfstests commit f2c179ef055d ("remove
    spurious _supported_fs calls").
    
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

diff --git a/test-appliance/files/root/runtests.sh b/test-appliance/files/root/runtests.sh
index f59305b0..817d51f2 100755
--- a/test-appliance/files/root/runtests.sh
+++ b/test-appliance/files/root/runtests.sh
@@ -386,6 +386,14 @@ do
 	    AEX="$AEX -E /tmp/exclude-tests"
 	fi
 	if test ! -f "$RESULT_BASE/tests-to-run" ; then
+	    case "$BASE_FSTYPE" in
+		ext2|ext3|ext4)
+		    tests_regexp="ext4"
+		    ;;
+		*)
+		    tests_regexp="$BASE_FSTYPE"
+	    esac
+	    tests_regexp="^($tests_regexp|shared|generic|perf|selftest)"
 	    bash ./check -n $FSTESTSET >& /tmp/tests-to-run.debug
 	    ret="$?"
 	    echo "Exit status $ret" >> /tmp/tests-to-run.debug
@@ -396,6 +404,7 @@ do
 	    fi
 	    bash ./check -n $FSTESTSET 2> /dev/null | \
 		sed -e '1,/^$/d' -e '/^$/d' | \
+		grep -E "$tests_regexp" | \
 		sort > "$RESULT_BASE/tests-to-run"
 	    nr_tests=$(wc -l < "$RESULT_BASE/tests-to-run")
 	    if test "$nr_tests" -ne 1

  reply	other threads:[~2024-07-15 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-14 14:00 [ANNOUNCE] fstests: for-next branch updated to v2024.07.14 Zorro Lang
2024-07-15 15:44 ` Theodore Ts'o [this message]
2024-07-15 19:50   ` Zorro Lang
2024-07-16 20:13     ` Theodore Ts'o
2024-07-17 15:21       ` Zorro Lang

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=20240715154454.GB70013@mit.edu \
    --to=tytso@mit.edu \
    --cc=fstests@vger.kernel.org \
    --cc=zlang@kernel.org \
    /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.