From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to 34c1208f601b
Date: Sun, 26 Jun 2022 16:49:15 +0800 [thread overview]
Message-ID: <20220626084917.BCAE2C34114@smtp.kernel.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 2846 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.06.26 release.
There's not new cases this week, nearly all cases fix/improvement. Just an
update on ext4/053 which brings in new test part, might fails on old kernel.
Thanks David Disseldorp, who is trying to add a new feature to help fstests to
loop run failed cases automatically (suggested by Ted). This week I haven't
merged that feature patchset, but merged 6 related pre-fix patches. More details
refer to:
https://lore.kernel.org/fstests/20220621160153.29591-1-ddiss@suse.de/
And welcome to try it, and give it your review points if you have. I'll try to
merge that feature in next release.
Thanks All!
Zorro
The new head of the for-next branch is commit:
34c1208f601b xfs/{422,517}: kill background jobs on test termination
New commits ([U]pdate):
Amir Goldstein (3):
[U] [4aa167d0d4d0] fstests: add missing _require_freeze() to tests
[U] [bc50d0f64a1b] fstests: unfreeze fs on cleanup routines
[U] [34c1208f601b] xfs/{422,517}: kill background jobs on test termination
David Disseldorp (6):
[U] [0730b5a94e0f] check: avoid FSTYP=<fstyp parameter> repetition
[U] [fdcff5481a86] check: simplify check.time parsing
[U] [40aa19bcc2f1] report: drop unused _xunit_make_section_report parameter
[U] [2b1016e1f507] report: fix xunit tests count
[U] [eda21d205f67] check: use arrays instead of separate n_ counters
[U] [0b0e82a4d755] check: remove err and first_test variables
Eric Biggers (1):
[U] [fc8c0d9f44dc] ext4/053: test changing test_dummy_encryption on remount
Eric Sandeen (1):
[U] [09f420da65a6] xfs/122: escape %zu in printf with %% not \\%
Luís Henriques (2):
[U] [ad794b00a3c2] generic/020: adjust max_attrval_size for ceph
[U] [b55aef7cfe6c] generic/486: adjust the max xattr size
Code Diffstat:
check | 148 ++++++++++++++++++++----------------------------
common/report | 14 +++--
src/attr_replace_test.c | 30 ++++++++--
tests/ext4/053 | 3 +
tests/generic/020 | 33 ++++++++---
tests/generic/068 | 14 +++--
tests/generic/085 | 3 +
tests/generic/280 | 13 ++++-
tests/generic/390 | 8 ++-
tests/generic/459 | 2 +
tests/generic/486 | 11 +++-
tests/generic/491 | 9 +++
tests/xfs/011 | 3 +-
tests/xfs/119 | 10 ++++
tests/xfs/122 | 4 +-
tests/xfs/297 | 11 ++++
tests/xfs/318 | 6 +-
tests/xfs/325 | 6 +-
tests/xfs/422 | 35 +++++++++++-
tests/xfs/438 | 4 +-
tests/xfs/517 | 27 ++++++++-
21 files changed, 270 insertions(+), 124 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-06-26 8:49 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=20220626084917.BCAE2C34114@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