FS/XFS testing framework
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: merge v2024.06.09 onto master branch
Date: Thu, 27 Jun 2024 17:39:54 +0800	[thread overview]
Message-ID: <143933ca68516410729c2a00ae524ee5@kernel.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2634 bytes --]

Hi all,

The master branch of the xfstests repository at:

	git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git

has just been updated to v2024.06.09 version.

Thanks,
Zorro

The new head of the master branch is commit:

83598d2f839d generic: test Btrfs fsync vs. size-extending prealloc write crash

New commits:

Darrick J. Wong (4):
      [ab6a3b1a0283] generic/747: redirect mkfs stderr to seqres.full
      [1a9ca7d53339] fuzzy: mask off a few more inode fields from the fuzz tests
      [d67b0d11106d] fuzzy: allow FUZZ_REWRITE_DURATION to control fsstress runtime when fuzzing
      [2da0c88e3481] fuzzy: test other dquot ids

Filipe Manana (2):
      [f50e6a3a7138] btrfs: fix raid-stripe-tree tests with non-experimental btrfs-progs build
      [887f00615ac4] btrfs/280: run defrag after creating file to get expected extent layout

Luis Henriques (SUSE) (1):
      [84de2df901bb] generic/077: ignore errors occurred while accessing the filler files

Omar Sandoval (1):
      [83598d2f839d] generic: test Btrfs fsync vs. size-extending prealloc write crash

Pankaj Raghav (3):
      [4fee7f2934ff] xfs/161: adapt the test case for 64k FS blocksize
      [edbea26d4c96] generic/436: round up bufsz to nearest filesystem blksz
      [97989c9839dd] xfs/008: use block size instead of the pagesize


Code Diffstat:

 check                  | 12 ++++++++++++
 common/filter.btrfs    |  4 ++--
 common/fuzzy           | 27 ++++++++++++++++++++++++---
 common/populate        | 14 ++++++++++++++
 src/seek_sanity_test.c |  8 ++++----
 tests/btrfs/280        | 10 +++++++++-
 tests/btrfs/304.out    |  6 ------
 tests/btrfs/305.out    |  6 ------
 tests/btrfs/306.out    |  6 ------
 tests/btrfs/307.out    |  6 ------
 tests/btrfs/308.out    |  6 ------
 tests/generic/077      |  8 ++++----
 tests/generic/747      |  2 +-
 tests/generic/748      | 45 +++++++++++++++++++++++++++++++++++++++++++++
 tests/generic/748.out  |  2 ++
 tests/xfs/008          | 20 +++++++++-----------
 tests/xfs/008.out      |  8 ++++----
 tests/xfs/161          | 16 ++++++++++++----
 tests/xfs/425          | 10 +++++++---
 tests/xfs/426          | 10 +++++++---
 tests/xfs/427          | 10 +++++++---
 tests/xfs/428          | 10 +++++++---
 tests/xfs/429          | 10 +++++++---
 tests/xfs/430          | 10 +++++++---
 tests/xfs/487          | 10 +++++++---
 tests/xfs/488          | 10 +++++++---
 tests/xfs/489          | 10 +++++++---
 tests/xfs/779          | 10 +++++++---
 tests/xfs/780          | 10 +++++++---
 tests/xfs/781          | 10 +++++++---
 30 files changed, 226 insertions(+), 100 deletions(-)
--
Zorro Lang
zlang@kernel.org

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

                 reply	other threads:[~2024-06-27  9:39 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=143933ca68516410729c2a00ae524ee5@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