FS/XFS testing framework
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to v2024.09.29
Date: Sun, 29 Sep 2024 21:37:31 +0800	[thread overview]
Message-ID: <f4d2a1fe4625b4f62ab5f8b01f55e12a@kernel.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2620 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.09.29 release.

Release Notes:
1) There're 8 new test cases in this release, include btrfs/322, ext4/060
   generic/365, xfs/629~632 and overlay/087.
2) The fsx.c is enhanced, it supports unshare range fallocate mode test. If
   you hit new failure on fsx test, please think about this change.

More details refer to below, thanks for all these contributions!

Thanks,
Zorro

The new head of the for-next branch is commit:

790f4d8444fa xfs: new EOF fragmentation tests

New commits ([N]ew, [U]pdate):

Amir Goldstein (1):
[N]      [d6433d8c8402] overlay: create a variant to syncfs error test xfs/546

Brian Foster (1):
[U]      [34ce77ce867d] fsx: support unshare range fallocate mode

Darrick J. Wong (1):
[N]      [c3140a6b8794] generic: add a regression test for sub-block fsmap queries

Dave Chinner (1):
[N]      [790f4d8444fa] xfs: new EOF fragmentation tests

Filipe Manana (4):
[U]      [9b41da945b20] fstests: add missing kernel git commit IDs to some tests
[U]      [185d797c73e1] fstests: fix min_dio_alignment logic for getting device block size
[U]      [10e6c6772b3d] btrfs/321: make the test work when compression is enabled
[N]      [d26d32028a78] btrfs: test an incremental send scenario with cloning of unaligned extent

Srivathsa Dara (1):
[N]      [7ba74c6a3c69] ext4: Regression test for corruption during on-line resize


Code Diffstat:

 ltp/fsx.c               |  67 ++++++++++++++++++++++-------
 src/min_dio_alignment.c |   2 +-
 tests/btrfs/321         |  10 +++--
 tests/btrfs/322         | 109 ++++++++++++++++++++++++++++++++++++++++++++++++
 tests/btrfs/322.out     |  24 +++++++++++
 tests/ext4/060          |  45 ++++++++++++++++++++
 tests/ext4/060.out      |   2 +
 tests/generic/364       |   2 +-
 tests/generic/365       |  79 +++++++++++++++++++++++++++++++++++
 tests/generic/365.out   |  15 +++++++
 tests/overlay/087       |  62 +++++++++++++++++++++++++++
 tests/overlay/087.out   |   4 ++
 tests/xfs/608           |   2 +-
 tests/xfs/629           |  67 +++++++++++++++++++++++++++++
 tests/xfs/629.out       |   9 ++++
 tests/xfs/630           |  70 +++++++++++++++++++++++++++++++
 tests/xfs/630.out       |   9 ++++
 tests/xfs/631           |  70 +++++++++++++++++++++++++++++++
 tests/xfs/631.out       |   9 ++++
 tests/xfs/632           |  78 ++++++++++++++++++++++++++++++++++
 tests/xfs/632.out       |  33 +++++++++++++++
 21 files changed, 745 insertions(+), 23 deletions(-)
--
Zorro Lang
zlang@kernel.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2024-09-29 13:37 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=f4d2a1fe4625b4f62ab5f8b01f55e12a@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