From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to 7d839ccc1a13
Date: Sun, 30 Oct 2022 19:06:44 +0800 [thread overview]
Message-ID: <20221030110647.784C1C433C1@smtp.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2964 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.30 release.
Release note:
1) There're 3 new cases (btrfs/278, xfs/554 and xfs/555) in this release.
They're all regression tests for known issue, xfs/555 might crash or hang
on kernel <= v3.14.
2) Encrypt test supports ceph fs, feel free to give it a try.
More update/improvement as below, thanks for all your contribution!
Thanks,
Zorro
The new head of the for-next branch is commit:
7d839ccc1a13 xfs: new test on xfs with corrupted sb_inopblock
New commits ([N]ew, [U]pdate):
BingJing Chang (1):
[N] [12f644786574] btrfs: test incremental send for orphan inodes
Darrick J. Wong (5):
[U] [65f937954f5e] populate: unexport the metadump description text
[U] [3cfd47b936e9] xfs: refactor filesystem feature detection logic
[U] [e33f8bfd0d70] xfs: refactor filesystem directory block size extraction logic
[U] [898ace3b1835] xfs: refactor filesystem realtime geometry detection logic
[U] [1153cd05b987] common: simplify grep pipe sed interactions
Hironori Shiina (1):
[N] [1ffa16c57368] xfs: test for fixing wrong root inode number in dump
Lukas Czerner (1):
[U] [2df0aa04659b] tests: Add missing _require_odirect from generic tests
Xiubo Li (1):
[U] [b38f94bbe96e] encrypt: add ceph support
Zorro Lang (1):
[N] [7d839ccc1a13] xfs: new test on xfs with corrupted sb_inopblock
Code Diffstat:
common/dump | 2 +-
common/encrypt | 3 +
common/ext4 | 9 ++
common/populate | 32 +++----
common/rc | 2 +-
common/xfs | 110 +++++++++++++++++++++---
src/Makefile | 2 +-
src/fake-dump-rootino.c | 224 ++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/278 | 218 ++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/278.out | 3 +
tests/generic/219 | 1 +
tests/generic/446 | 1 +
tests/generic/459 | 1 +
tests/generic/569 | 1 +
tests/generic/570 | 1 +
tests/generic/587 | 1 +
tests/xfs/097 | 2 +-
tests/xfs/099 | 2 +-
tests/xfs/100 | 2 +-
tests/xfs/101 | 2 +-
tests/xfs/102 | 2 +-
tests/xfs/105 | 2 +-
tests/xfs/112 | 2 +-
tests/xfs/113 | 2 +-
tests/xfs/146 | 2 +-
tests/xfs/147 | 2 +-
tests/xfs/151 | 3 +-
tests/xfs/271 | 2 +-
tests/xfs/307 | 2 +-
tests/xfs/308 | 2 +-
tests/xfs/348 | 2 +-
tests/xfs/530 | 3 +-
tests/xfs/554 | 75 ++++++++++++++++
tests/xfs/554.out | 40 +++++++++
tests/xfs/555 | 32 +++++++
tests/xfs/555.out | 6 ++
36 files changed, 748 insertions(+), 50 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-10-30 11:06 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=20221030110647.784C1C433C1@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