From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: merge v2024.11.17 onto master branch
Date: Sun, 01 Dec 2024 21:38:03 +0800 [thread overview]
Message-ID: <08c64977b30bd55f30f5a366c81851e5@kernel.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 3177 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 v2024.11.17 version.
Thanks,
Zorro
The new head of the master branch is commit:
88be6071da67 xfs/185: don't fail when rtfile is larger than rblocks
New commits:
Alexander Mikhalitsyn (1):
[cdbcb808ecc1] ext4/032: add a new testcase in online resize tests
André Almeida (1):
[c3a28053dc09] common/casefold: Support for tmpfs casefold test
Brian Foster (2):
[2fe95b92d6da] xfs: online grow vs. log recovery stress test
[083bb0ea9473] xfs: online grow vs. log recovery stress test (realtime version)
Chao Yu (3):
[5089b050a672] f2fs/005: add testcase to check checkpoint disabling functionality
[23ebca50151d] f2fs/006: add testcase to check out-of-space case
[7838e3082b15] f2fs/007: add testcase to check consistency of compressed inode metadata
Darrick J. Wong (2):
[47aa187fb226] xfs/273: check thoroughness of the mappings
[88be6071da67] xfs/185: don't fail when rtfile is larger than rblocks
Filipe Manana (2):
[d9228b41b30f] btrfs/287: make the test work when compression is enabled
[1e990ee9aaa0] btrfs: add a test for defrag of contiguous file extents
Johannes Thumshirn (1):
[e2affc453cf5] btrfs/136: check for ext3 support
Qu Wenruo (3):
[4c1629ae3a3a] generic: new test case to verify if certain fio load will hang the filesystem
[81477600d363] btrfs: a new test case to verify mount behavior with background remounting
[3fc00cd4ab98] btrfs/321: make the filter to handle older btrfs-progs
Zorro Lang (1):
[66434a1cb731] xfs: notrun if kernel xfs not supports ascii-ci feature
Code Diffstat:
common/casefold | 46 +++++++++++++++++++++
common/rc | 3 ++
common/xfs | 10 +++++
tests/btrfs/136 | 2 +
tests/btrfs/287 | 10 ++---
tests/btrfs/287.out | 4 --
tests/btrfs/321 | 2 +-
tests/btrfs/325 | 83 ++++++++++++++++++++++++++++++++++++++
tests/btrfs/325.out | 22 ++++++++++
tests/btrfs/326 | 107 +++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/326.out | 2 +
tests/ext4/032 | 6 +++
tests/ext4/032.out | 18 +++++++++
tests/f2fs/005 | 47 ++++++++++++++++++++++
tests/f2fs/005.out | 2 +
tests/f2fs/006 | 42 ++++++++++++++++++++
tests/f2fs/006.out | 2 +
tests/f2fs/007 | 108 ++++++++++++++++++++++++++++++++++++++++++++++++++
tests/f2fs/007.out | 16 ++++++++
tests/generic/366 | 106 +++++++++++++++++++++++++++++++++++++++++++++++++
tests/generic/366.out | 2 +
tests/generic/556 | 12 ++++--
tests/xfs/185 | 6 ++-
tests/xfs/188 | 1 +
tests/xfs/273 | 47 ++++++++++++++++++++++
tests/xfs/597 | 1 +
tests/xfs/598 | 1 +
tests/xfs/609 | 79 ++++++++++++++++++++++++++++++++++++
tests/xfs/609.out | 2 +
tests/xfs/610 | 81 +++++++++++++++++++++++++++++++++++++
tests/xfs/610.out | 2 +
31 files changed, 856 insertions(+), 16 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2024-12-01 13:38 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=08c64977b30bd55f30f5a366c81851e5@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