From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: merge v2022.07.10 onto master branch
Date: Sun, 24 Jul 2022 22:05:32 +0800 [thread overview]
Message-ID: <20220724140538.18A70C3411E@smtp.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1587 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 v2022.07.10 version (merged from for-next).
Thanks,
Zorro
The new head of the master branch is commit:
47ed06630971 xfs/144: fix test mkfs.xfs sizing of internal logs that overflow the AG
New commits:
Christoph Hellwig (1):
[d3eb6a2b1599] btrfs: test raid1 write error handling
Darrick J. Wong (4):
[6ecd4b5b7cd9] xfs/288: skip repair -n when checking empty root leaf block behavior
[c9ef32ad6e38] xfs: make sure that we handle empty xattr leaf blocks ok
[daba59ddecf3] xfs/547: fix problems with realtime
[47ed06630971] xfs/144: fix test mkfs.xfs sizing of internal logs that overflow the AG
David Disseldorp (5):
[de1fda54e5f0] report: use array for REPORT_ENV_LIST
[e47930fb73bc] report: pass through most details as function parameters
[5c31ba9b7299] check: make a few variables local
[6bae394bcd50] check: append bad / notrun arrays in helper function
[2fe10922349c] check: add -L <n> parameter to rerun failed tests
Code Diffstat:
check | 137 ++++++++++----
common/report | 90 +++++----
tests/btrfs/271 | 78 ++++++++
tests/btrfs/271.out | 521 ++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/144 | 14 +-
tests/xfs/191 | 117 ++++++++++++
tests/xfs/191.out | 7 +
tests/xfs/288 | 32 ++--
tests/xfs/547 | 14 +-
9 files changed, 899 insertions(+), 111 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-07-24 14: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=20220724140538.18A70C3411E@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