From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: merge v2026.02.26 onto master branch
Date: Fri, 20 Mar 2026 18:11:40 +0800 [thread overview]
Message-ID: <2c426292a3ab7aec770bb7d7c0cbefaa@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2583 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.02.26 version.
Thanks,
Zorro
The new head of the master branch is commit:
3ded3e13c008 tests: Fix failure in nojournal mode
New commits:
Andrey Albershteyn (1):
[6fe19be2ecc1] generic/579: handle quoted cmp output
Christoph Hellwig (2):
[1ec21c2911f3] generic: test that truncate(2) on fsverity is blocked
[163dbbfaacf0] xfs/841: create a block device that must exist
Darrick J. Wong (3):
[98dd6070d7eb] xfs/018: remove inline xattr recovery tests
[08989d57ae35] xfs/620: force xattr leaf format for this test
[d290a3c1b673] generic/749: don't write a ton of _mread output to seqres.full
Filipe Manana (2):
[6cc08eb81328] generic: add missing kernel commit IDs to tests 784 and 785
[75bbf15c5629] generic: test fsync of a file truncated to a length of zero
Jan Kara (1):
[3ded3e13c008] tests: Fix failure in nojournal mode
Joanne Chang (1):
[66c8f2df3f3a] common/rc: add _require_max_file_range_blocks helper
Qu Wenruo (2):
[eeb894a242c8] fstests: btrfs: add a regression test for incorrect inode incompressible flag
[c26276f53d58] fstests: btrfs: add a test case for failed compressed inline attempt
Code Diffstat:
.gitignore | 1 +
common/rc | 16 ++++++++++++++
src/Makefile | 2 +-
src/truncate.c | 17 +++++++++++++++
tests/btrfs/343 | 48 +++++++++++++++++++++++++++++++++++++++++
tests/btrfs/343.out | 2 ++
tests/btrfs/344 | 53 +++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/344.out | 2 ++
tests/ext4/051 | 1 +
tests/generic/536 | 1 +
tests/generic/579 | 1 +
tests/generic/622 | 1 +
tests/generic/635 | 1 +
tests/generic/646 | 1 +
tests/generic/705 | 1 +
tests/generic/722 | 1 +
tests/generic/735 | 1 +
tests/generic/749 | 11 +++++++---
tests/generic/784 | 2 +-
tests/generic/785 | 2 +-
tests/generic/788 | 38 +++++++++++++++++++++++++++++++++
tests/generic/788.out | 4 ++++
tests/generic/789 | 59 +++++++++++++++++++++++++++++++++++++++++++++++++++
tests/generic/789.out | 5 +++++
tests/overlay/087 | 1 +
tests/xfs/018 | 24 ---------------------
tests/xfs/018.out | 45 ---------------------------------------
tests/xfs/620 | 7 ++++--
tests/xfs/841 | 5 ++++-
29 files changed, 275 insertions(+), 78 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2026-03-20 10:11 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=2c426292a3ab7aec770bb7d7c0cbefaa@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