public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: merge v2026.01.27 onto master branch
Date: Thu, 26 Feb 2026 00:25:42 +0800	[thread overview]
Message-ID: <680e30e02982bf96d6749d431609f1aa@kernel.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2665 bytes --]

Hi all,

The master branch of the xfstests repository at:

	git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git

has just been updated to v2026.01.27 version.

Thanks,
Zorro

The new head of the master branch is commit:

69cd20bd0498 xfs: test reproducible builds

New commits:

Darrick J. Wong (2):
      [754368070ac5] xfs/614: fix test for parent pointers
      [31f7192f90a8] misc: allow zero duration for fsstress and fsx

Filipe Manana (2):
      [8dad086a4701] btrfs: test power failure after fsync and rename exchanging directories
      [e0ded76267f9] fsx: add missing -T option to getopt_long()

Jaegeuk Kim (1):
      [096adc20b3df] f2fs/015: Test correct mkfs options for error cases

Luca Di Maio (1):
      [69cd20bd0498] xfs: test reproducible builds

Nirjhar Roy (IBM) (1):
      [725b08a6d61a] generic/371: Fix the test to be compatible block sizes upto 64k

Ojaswin Mujoo (1):
      [a4dbdc5486b4] generic/108: fix test hand upon failure to create LV

Qu Wenruo (2):
      [8d2e1bd3d294] fstests: btrfs/131: add explicit v1 space cache requirement
      [bc74aaf6859c] fstests: btrfs: add a new test case that is future-proof

Viacheslav Dubeyko (1):
      [facf3325d90d] xfstests: hfs/hfsplus don't support metadata journaling

caokewu (1):
      [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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2026-02-25 16:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=680e30e02982bf96d6749d431609f1aa@kernel.org \
    --to=zlang@kernel.org \
    --cc=fstests@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