From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 3/3] btrfs-progs: convert-tests/022: add reiserfs support check
Date: Thu, 6 Oct 2022 17:29:24 +0200 [thread overview]
Message-ID: <20221006152924.GO13389@twin.jikos.cz> (raw)
In-Reply-To: <feae908d2bfe2e92efc26f4cef5d8ddf186c7114.1664936628.git.wqu@suse.com>
On Wed, Oct 05, 2022 at 10:25:14AM +0800, Qu Wenruo wrote:
> [BUG]
> Btrfs-progs test case convert/022 will fail if the system doesn't have
> reiserfs support nor reiserfs user space tools:
>
> # make TEST=022\* test-convert
> [TEST] convert-tests.sh
> WARNING: reiserfs filesystem not listed in /proc/filesystems, some tests might be skipped
> [TEST/conv] 022-reiserfs-parent-ref
> Failed system wide prerequisities: mkreiserfs
> test failed for case 022-reiserfs-parent-ref
> make: *** [Makefile:443: test-convert] Error 1
>
> [CAUSE]
> Unlike other test cases, convert/022 doesn't even check if we have
> kernel support for it.
>
> [FIX]
> Add the proper check before doing system wide prerequisities checks.
I've moved it before the mkreiserfs check, I'd like to keep the
setup_root_helper and prepare_test_dev first in the list for
consistency.
next prev parent reply other threads:[~2022-10-06 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 2:25 [PATCH 0/3] btrfs-progs: selftests fixes Qu Wenruo
2022-10-05 2:25 ` [PATCH 1/3] btrfs-progs: tests: fix the wrong kernel version check Qu Wenruo
2022-10-06 15:25 ` David Sterba
2022-10-05 2:25 ` [PATCH 2/3] btrfs-progs: mkfs-tests/025: fix the wrong function call Qu Wenruo
2022-10-05 6:43 ` Wang Yugui
2022-10-05 7:58 ` Qu Wenruo
2022-10-05 11:50 ` David Sterba
2022-10-05 2:25 ` [PATCH 3/3] btrfs-progs: convert-tests/022: add reiserfs support check Qu Wenruo
2022-10-06 15:29 ` David Sterba [this message]
2022-10-06 15:30 ` [PATCH 0/3] btrfs-progs: selftests fixes David Sterba
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=20221006152924.GO13389@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@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