All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Zorro Lang <zlang@kernel.org>
Cc: fstests@vger.kernel.org
Subject: Re: [ANNOUNCE] fstests: for-next branch updated to v2026.01.27
Date: Tue, 27 Jan 2026 07:47:15 -0800	[thread overview]
Message-ID: <20260127154715.GC5916@frogsfrogsfrogs> (raw)
In-Reply-To: <e722a754c0ae8ed500fcdc16736a9202@kernel.org>

On Tue, Jan 27, 2026 at 02:58:36PM +0800, Zorro Lang wrote:
> Hi all,
> 
> The for-next branch of the xfstests repository at:
> 
> 	git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
> 
> has just been updated and tagged as v2026.01.27 release.

I see that master did indeed jump to the Jan 5 tag, but for-next still
seems to be at v2026.01.05?

--D

> Release Notes:
> 1) There're 3 new test cases in this release, includes btrfs/341, btrfs/342 and
>    xfs/841.
> 2) fsstress and fsx don't fail when --duration=0.
> 
> More fixes on btrfs, ext4, f2fs, hfs and xfs, please refer to the details below.
> Thanks for all these contributions.
> 
> Thanks,
> Zorro
> 
> The new head of the for-next branch is commit:
> 
> 69cd20bd0498 xfs: test reproducible builds
> 
> New commits ([N]ew, [U]pdate):
> 
> Darrick J. Wong (2):
> [U]      [754368070ac5] xfs/614: fix test for parent pointers
> [U]      [31f7192f90a8] misc: allow zero duration for fsstress and fsx
> 
> Filipe Manana (2):
> [N]      [8dad086a4701] btrfs: test power failure after fsync and rename exchanging directories
> [U]      [e0ded76267f9] fsx: add missing -T option to getopt_long()
> 
> Jaegeuk Kim (1):
> [U]      [096adc20b3df] f2fs/015: Test correct mkfs options for error cases
> 
> Luca Di Maio (1):
> [N]      [69cd20bd0498] xfs: test reproducible builds
> 
> Nirjhar Roy (IBM) (1):
> [U]      [725b08a6d61a] generic/371: Fix the test to be compatible block sizes upto 64k
> 
> Ojaswin Mujoo (1):
> [U]      [a4dbdc5486b4] generic/108: fix test hand upon failure to create LV
> 
> Qu Wenruo (2):
> [U]      [8d2e1bd3d294] fstests: btrfs/131: add explicit v1 space cache requirement
> [N]      [bc74aaf6859c] fstests: btrfs: add a new test case that is future-proof
> 
> Viacheslav Dubeyko (1):
> [U]      [facf3325d90d] xfstests: hfs/hfsplus don't support metadata journaling
> 
> caokewu (1):
> [U]      [42c2ccaf3700] ext4/307: allocate donor file size dynamically
> 
> 
> Code Diffstat:
> 
>  common/btrfs                     |  25 ++++++
>  common/rc                        |   2 +-
>  common/xfs                       |   3 +
>  ltp/fsstress.c                   |   5 +-
>  ltp/fsx.c                        |   7 +-
>  tests/btrfs/131                  |  12 ++-
>  tests/btrfs/341                  |  73 ++++++++++++++++
>  tests/btrfs/341.out              |  15 ++++
>  tests/btrfs/342                  | 103 +++++++++++++++++++++++
>  tests/btrfs/342.out              |  15 ++++
>  tests/ext4/307                   |   5 +-
>  tests/f2fs/015                   |  10 ++-
>  tests/f2fs/015.out               |  92 ++++++++++----------
>  tests/generic/108                |   7 +-
>  tests/generic/371                |   2 +-
>  tests/xfs/614                    |   1 +
>  tests/xfs/614.cfg                |   4 +
>  tests/xfs/614.out.lba1024_parent | 177 +++++++++++++++++++++++++++++++++++++++
>  tests/xfs/614.out.lba2048_parent | 177 +++++++++++++++++++++++++++++++++++++++
>  tests/xfs/614.out.lba4096_parent | 177 +++++++++++++++++++++++++++++++++++++++
>  tests/xfs/614.out.lba512_parent  | 177 +++++++++++++++++++++++++++++++++++++++
>  tests/xfs/841                    | 173 ++++++++++++++++++++++++++++++++++++++
>  tests/xfs/841.out                |   3 +
>  23 files changed, 1205 insertions(+), 60 deletions(-)
> --
> Zorro Lang
> zlang@kernel.org



  reply	other threads:[~2026-01-27 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27  6:58 [ANNOUNCE] fstests: for-next branch updated to v2026.01.27 Zorro Lang
2026-01-27 15:47 ` Darrick J. Wong [this message]
2026-01-29  8:17   ` 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=20260127154715.GC5916@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --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.