public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, kdevops@lists.linux.dev
Subject: Re: btrfs v6.15-rc2 baseline
Date: Thu, 24 Apr 2025 12:17:36 +0200	[thread overview]
Message-ID: <20250424101736.GL3659@suse.cz> (raw)
In-Reply-To: <Z__4Fu6VsCVDFKkO@bombadil.infradead.org>

On Wed, Apr 16, 2025 at 11:33:58AM -0700, Luis Chamberlain wrote:
> btrfs developers,
> 
> kdevops has run fstests on v6.15-rc2 across the different btrfs profiles
> it currently defines, and the results are below.
> 
> The btrfs profiles which kdevops currently supports are:
> 
>   - btrfs_simple
>   - btrfs_nohofspace
>   - btrfs_noholes
>   - btrfs_holes
>   - btrfs_holes_zstd
>   - btrfs_noholes_lzo
>   - btrfs_fspace
>   - btrfs_noholes_zlib
>   - btrfs_noholes_zstd

I don't know how much VM power you have to run all the setups, some of
thhem can be removed as they are duplicating the defaults. We've
switched to 'noholes' by default, so anything with 'holes' can be
removed. Same with free space tree (space_cache=v2).

> These are defined in the btrfs jinja2 template on kdevops [0] and described
> on the ext4 kconfig [1]. Adding support for more profiles is just a matter
> of editing these two files, please feel free to send a patch if you'd like
> kdevops to test more profiles. A full tarball of the fstests results are
> available on kdevops-results-archive [2]. Since we leverage git-lfs, you can
> opt to only download this single tarball as follows:
> 
> GIT_LFS_SKIP_SMUDGE=1 git clone https://github.com/linux-kdevops/kdevops-results-archive.git
> cd kdevops-results-archive
> git lfs fetch --include "fstests/gh/linux-btrfs-kpd/20250416/0001/linux-6-15-rc2/8ffd015db85f.xz"
> git lfs checkout "fstests/gh/linux-btrfs-kpd/20250416/0001/linux-6-15-rc2/8ffd015db85f.xz"
> 
> Few questions:
> 
>  - Is this useful information?

Yes.

>  - Do you want results for each rc release posted to the mailing list?

Yes, ideally in some terse form with the summary lines only, the full
list of Failures seems too much. Tuning fstests to run with 0 failures
involves adding expunges/excludes or other workarounds.

Another idea is to post only the diff from one week to another, once
some baseline is established.

> 
> [0] https://github.com/linux-kdevops/kdevops/blob/main/playbooks/roles/fstests/templates/btrfs/btrfs.config
> [1] https://github.com/linux-kdevops/kdevops/blob/main/workflows/fstests/btrfs/Kconfig

There are some configured options that are default, like the
discard=async, so they can be removed for the configs related to
mainline.

  parent reply	other threads:[~2025-04-24 10:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 18:33 btrfs v6.15-rc2 baseline Luis Chamberlain
2025-04-16 19:12 ` Boris Burkov
2025-04-16 19:39   ` Luis Chamberlain
2025-04-17  9:04 ` Johannes Thumshirn
2025-04-18  1:44   ` Luis Chamberlain
2025-04-17 10:15 ` Qu Wenruo
2025-04-18  2:02   ` Luis Chamberlain
2025-04-24 10:17 ` David Sterba [this message]
2025-04-29 19:58   ` Luis Chamberlain

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=20250424101736.GL3659@suse.cz \
    --to=dsterba@suse.cz \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=kdevops@lists.linux.dev \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mcgrof@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