From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: tests: not_run for global_prereq fail
Date: Fri, 28 Jul 2023 11:51:18 +0800 [thread overview]
Message-ID: <12e88a5b-59d1-4403-f9b6-37ec23866e77@oracle.com> (raw)
In-Reply-To: <155356de-ddfc-118c-eaaa-9dca8f2401a1@oracle.com>
On 28/07/2023 11:39, Anand Jain wrote:
> On 28/07/2023 00:51, David Sterba wrote:
>> On Tue, Jul 25, 2023 at 05:43:54PM +0800, Anand Jain wrote:
>>> Prerequisite checks using global_prereq() aren't global, so why
>>> fail and stop further test cases? Instead, just don't run them.
>>
>> I'd rather let the whole testsuite run, a missing global prerequisity
>> means the environment is not set up properly, so this fail as intended.
>> If you look what kind of utilities are checked in that way it's eg. dd,
>> mke2fs, chattr, losetup. All are supposed to be available on a common
>> system so it's not expected to fail.
>>
>> If there's some less common utility and a test which could be optional
>> then this should be a special case, which would require a new helper.
>
> I would prefer using check_global_prereq() to verify all the mandatory
> prerequisites at once.
>
> If each test case checks for a different binary using
> check_global_prereq() and it fails during that test case, we have to
> restart, which becomes messy.
Commit 'btrfs-progs: tests: add script to check global prerequisities'
addressed the messy situation mentioned above.
> The support for mkreiserfs on OL was removed, causing the test case
> to abruptly stop in the middle.
Is there a way to skip the test cases?
next prev parent reply other threads:[~2023-07-28 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 9:43 [PATCH] btrfs-progs: tests: not_run for global_prereq fail Anand Jain
2023-07-27 16:51 ` David Sterba
2023-07-28 3:39 ` Anand Jain
2023-07-28 3:51 ` Anand Jain [this message]
2023-08-11 17:57 ` 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=12e88a5b-59d1-4403-f9b6-37ec23866e77@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).