From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to v2024.07.28
Date: Mon, 29 Jul 2024 00:09:31 +0800 [thread overview]
Message-ID: <74eba5b56b78f2d6b465fae7c3262ad9@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2299 bytes --]
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 v2024.07.28 release.
Release Notes:
1) There're 3 new test cases in this release, include btrfs/312, f2fs/003
and f2fs/004.
2) More updates and fixes for xfs and btrfs.
Thanks for all these contributions.
Zorro
The new head of the for-next branch is commit:
f5ada754d583 generic/754: fix _fixed_by tags
New commits ([N]ew, [U]pdate):
Chao Yu (2):
[N] [c62c3d1cfbc7] f2fs: test for race condition in between atomic_write and gc
[N] [410ab2ebf3b8] f2fs: test for race condition in between atomic_write and dio
Christoph Hellwig (2):
[U] [7cb775459424] xfs/011: support byte-based grant heads are stored in bytes now
[U] [0bc89993579b] xfs: add a few more tests to the repair group
Darrick J. Wong (1):
[U] [f5ada754d583] generic/754: fix _fixed_by tags
David Sterba (1):
[U] [9b6922eb610c] btrfs/220: remove integrity checker bits
Filipe Manana (2):
[N] [592f6a79f56e] btrfs: test a compressed send stream scenario that triggered a read corruption
[U] [02a689b7aa07] btrfs: properly shutdown subvolume stress worker to avoid umount failures
Qu Wenruo (1):
[U] [b548b23fd4e9] fstests: btrfs/012: fix a false alert due to socket/pipe files
Code Diffstat:
common/btrfs | 2 +
tests/btrfs/012 | 29 +++++++------
tests/btrfs/012.out | 6 +++
tests/btrfs/060 | 9 ++--
tests/btrfs/065 | 9 ++--
tests/btrfs/066 | 9 ++--
tests/btrfs/067 | 9 ++--
tests/btrfs/068 | 9 ++--
tests/btrfs/220 | 5 ---
tests/btrfs/312 | 115 ++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/312.out | 7 ++++
tests/f2fs/003 | 65 +++++++++++++++++++++++++++++
tests/f2fs/003.out | 11 +++++
tests/f2fs/004 | 48 ++++++++++++++++++++++
tests/f2fs/004.out | 3 ++
tests/generic/754 | 7 +++-
tests/xfs/011 | 77 ++++++++++++++++++++++++-----------
tests/xfs/337 | 2 +-
tests/xfs/338 | 2 +-
tests/xfs/339 | 2 +-
tests/xfs/340 | 2 +-
tests/xfs/341 | 2 +-
tests/xfs/342 | 2 +-
23 files changed, 364 insertions(+), 68 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2024-07-28 16:09 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=74eba5b56b78f2d6b465fae7c3262ad9@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