From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to 3b5cb74c0331
Date: Sun, 09 Oct 2022 20:38:15 +0800 [thread overview]
Message-ID: <20221009123818.C1EB2C433D6@smtp.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2513 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 v2022.10.09 release.
Release notes:
1) There're 2 new btrfs specific cases -- btrfs/273 and btrfs/276. The former is
a known regression test, the later is a new testing coverage but don't have
known bug/fix for it.
2) A new common file (common/zoned) is added in fstests, welcome more zoned block
device related testing add helpers into this file.
Thanks for all your contribution! More details refor to below.
Thanks,
Zorro
The new head of the for-next branch is commit:
3b5cb74c0331 common/populate: fix _xfs_metadump usage in _scratch_populate_cached
New commits ([N]ew file/test, [U]pdate):
Darrick J. Wong (6):
[U] [41914271ff11] generic/092: skip test if file allocation unit isn't aligned
[U] [7bac64cc78dd] xfs/114: fix missing reflink requires
[U] [62d628f7bb71] xfs/229: do not _xfs_force_bdev on TEST_DIR
[U] [a2d5043aca59] xfs/128: try to force file allocation behavior
[U] [796546224dee] common/populate: don't metadump xfs filesystems twice
[U] [3b5cb74c0331] common/populate: fix _xfs_metadump usage in _scratch_populate_cached
Filipe Manana (1):
[N] [8088eb0a46cc] btrfs: test fiemap on large file with extents shared through a snapshot
Naohiro Aota (2):
[N] [18b44df21afc] common: introduce zone_capacity() to return a zone capacity
[N] [dcf2ada66e2d] btrfs: test active zone tracking
Pavel Reichl (2):
[U] [ce018e24f0a5] cleanup: remove left files after test finishes
[U] [b57788fbe2cd] generic/299: skip test early if falloc is not supported
Code Diffstat:
common/filter | 13 -----
common/populate | 3 +-
common/rc | 1 +
common/xfs | 3 ++
common/zoned | 39 ++++++++++++++
tests/btrfs/237 | 8 +--
tests/btrfs/273 | 143 ++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/273.out | 2 +
tests/btrfs/276 | 124 +++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/276.out | 16 ++++++
tests/generic/092 | 6 +++
tests/generic/285 | 2 +-
tests/generic/299 | 2 +-
tests/generic/394 | 2 +-
tests/generic/436 | 2 +-
tests/generic/445 | 2 +-
tests/generic/448 | 2 +-
tests/xfs/114 | 2 +
tests/xfs/128 | 34 +++++++++++--
tests/xfs/229 | 7 ++-
20 files changed, 381 insertions(+), 32 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-10-09 12: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=20221009123818.C1EB2C433D6@smtp.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