All of lore.kernel.org
 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.10.28
Date: Mon, 28 Oct 2024 01:24:35 +0800	[thread overview]
Message-ID: <a358e7958c8cdc17c0dea13d169a2be3@kernel.org> (raw)

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

Release Notes:
1) There're 3 new test cases in this release, include btrfs/323, btrfs/324,
   and generic/757. All of them cover known btrfs regression issues.
2) More cases are fixed for Large Block Size testing. Welcome more testing
   and fixing for that :)

More updates and fixes on xfs and btrfs, thanks for all of these contributions!

Thanks,
Zorro

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

f056971a4d2f btrfs: test remount with "compress" clears "compress-force"

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

Boris Burkov (1):
[N]      [9eda73ff4695] btrfs: add test for cleaner thread under seed-sprout

Chao Yu (1):
[U]      [18795160b0f3] f2fs/004: add missing _fixed_by_kernel_commit line

Darrick J. Wong (2):
[U]      [1f8fedd08f06] common/xfs: _notrun tests that fail due to block size < sector size
[U]      [9c3762ceafd4] misc: amend unicode confusing name tests to check for hidden tag characters

Filipe Manana (1):
[N]      [f056971a4d2f] btrfs: test remount with "compress" clears "compress-force"

Mark Harmstone (1):
[N]      [cf97fa373d61] generic: add test for missing btrfs csums in log when doing async on subpage vol

Pankaj Raghav (3):
[U]      [bd0d0179baf1] xfs/161: adapt the test case for LBS filesystem
[U]      [b71de9073a65] generic/219: use filesystem blocksize while calculating the file size
[U]      [6d97ae8ddebf] generic: increase file size to match CoW delayed allocation for XFS 64k bs

Qu Wenruo (3):
[U]      [0d203737049d] btrfs/012: fix false alerts when SELinux is enabled
[U]      [0ee667ece05c] fstests: btrfs/330: enable the test case for both new and old APIs
[U]      [6f4a6b5789d7] fstests: btrfs/002: fix the OOM caused by too large block size


Code Diffstat:

 common/xfs            |  5 ++++
 tests/btrfs/002       | 14 ++++-----
 tests/btrfs/012       |  5 ++++
 tests/btrfs/323       | 47 ++++++++++++++++++++++++++++++
 tests/btrfs/323.out   |  4 +++
 tests/btrfs/324       | 39 +++++++++++++++++++++++++
 tests/btrfs/324.out   |  2 ++
 tests/btrfs/330       |  9 ++++--
 tests/f2fs/004        |  3 ++
 tests/generic/219     | 18 ++++++++++--
 tests/generic/305     |  2 +-
 tests/generic/305.out | 12 ++++----
 tests/generic/326     |  2 +-
 tests/generic/326.out | 12 ++++----
 tests/generic/328     |  2 +-
 tests/generic/328.out | 16 ++++++-----
 tests/generic/453     |  8 ++++++
 tests/generic/454     | 29 ++++++++++++-------
 tests/generic/757     | 80 +++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/generic/757.out |  2 ++
 tests/xfs/161         |  6 +++-
 tests/xfs/504         |  3 ++
 22 files changed, 272 insertions(+), 48 deletions(-)
--
Zorro Lang
zlang@kernel.org

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

                 reply	other threads:[~2024-10-27 17:24 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=a358e7958c8cdc17c0dea13d169a2be3@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.