From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to v2024.12.22
Date: Sun, 22 Dec 2024 22:33:44 +0800 [thread overview]
Message-ID: <f181e6f3383c1e9db12c16abcb2a268c@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2121 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.12.22 release.
Release Note:
Since a big feature updated on last version, we get some updates and fixes for
stable this time. There's not new test case in this release. More details
refer to below.
Thanks,
Zorro
The new head of the for-next branch is commit:
023070744cef generic/530: only use xfs-specific mkfs options when testing on xfs
New commits:
Chao Yu (1):
[4a33c5b1dd0c] f2fs: add commit id to _fixed_by_kernel_commit
Christoph Hellwig (3):
[2b66be5f5cfc] common: loop device work on zoned file systems
[825950c8cab7] common: cleanup scratch_mkfs_sized
[3b9f5fc7d7d8] common: call _require_scratch_dedupe from _require_scratch_duperemove
Filipe Manana (6):
[1f32af6a4ce9] fstests: fix argument passing to _run_fsstress and _run_fsstress_bg
[06626fb70ae7] btrfs/100, btrfs/101: fix device name in their golden output
[9b12a1a8a35b] btrfs/142, btrfs/143: fix dmdust device names
[8212e1ada5e0] btrfs/146: fix failure due to missing test number argument for fsync-err
[7c5604ec86b8] generic/442: fix failure due to missing test number argument for fsync-err
[a1d583fa0062] generic/590: fix test failure when running against fs other than xfs
Theodore Ts'o (2):
[f7262fd49cf8] generic/135: don't try to rm $SCRATCH_MNT/*
[023070744cef] generic/530: only use xfs-specific mkfs options when testing on xfs
Code Diffstat:
common/rc | 24 ++++++++++++------------
common/reflink | 2 ++
tests/btrfs/100.out | 2 +-
tests/btrfs/101.out | 2 +-
tests/btrfs/142 | 4 ++--
tests/btrfs/143 | 4 ++--
tests/btrfs/146 | 2 +-
tests/f2fs/005 | 2 +-
tests/f2fs/006 | 2 +-
tests/f2fs/007 | 2 +-
tests/generic/135 | 2 --
tests/generic/442 | 2 +-
tests/generic/530 | 9 ++++++++-
tests/generic/563 | 4 ++++
tests/generic/590 | 2 --
15 files changed, 37 insertions(+), 28 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2024-12-22 14:33 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=f181e6f3383c1e9db12c16abcb2a268c@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