linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: tests/misc/030: do not require v1 cache for the test case
Date: Wed, 9 Aug 2023 09:18:25 -0400	[thread overview]
Message-ID: <20230809131825.GD2515439@perftesting> (raw)
In-Reply-To: <c56a81542acc3319265ed1041640253d2b4b8276.1691474892.git.wqu@suse.com>

On Tue, Aug 08, 2023 at 02:08:42PM +0800, Qu Wenruo wrote:
> [PROBLEM]
> Since we have migrated to default v2 cache, the test case
> misc/030-missing-device-image is no longer executed:
> 
>     [TEST/misc]   030-missing-device-image
>     [NOTRUN] unable to create v1 space cache
> 
> [CAUSE]
> The test case itself is trying its best to cover all paths, including
> the data extent read path.
> 
> Thus the test case is requiring v1 cache, as that's the only way to
> cover the data read path.
> 
> [FIX]
> Just remove the v1 space cache requirement, it's still better to run the
> test even it only exercises the metadata read path.
> 
> The good news is, after commit 3ff9d352576b ("btrfs-progs: use
> read_data_from_disk() to replace read_extent_from_disk() and replace
> read_extent_data()"), all data/metadata read paths are unified.
> They only differ in the verification part.
> 
> Thus even if we didn't fully exercise the data read path, we didn't lose
> much coverage anyway.
> 
> Signed-off-by: Qu Wenruo <wqu@suse.com>

Reviewed-by: Josef Bacik <josef@toxicpanda.com>

Thanks,

Josef

      reply	other threads:[~2023-08-09 13:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08  6:08 [PATCH] btrfs-progs: tests/misc/030: do not require v1 cache for the test case Qu Wenruo
2023-08-09 13:18 ` Josef Bacik [this message]

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=20230809131825.GD2515439@perftesting \
    --to=josef@toxicpanda.com \
    --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;
as well as URLs for NNTP newsgroup(s).