From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to 68d2ebf90d94
Date: Sun, 05 Nov 2017 16:31:25 +0800 [thread overview]
Message-ID: <59fecc65.019c620a.2c7a4.e533@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3179 bytes --]
Hi all,
The master branch of the xfstests repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
have just been updated. It mainly contains various fixes from Darrick for
preparation of xfs_scrub and the comming xfs updates in v4.15 merge window, but
there're also new tests for btrfs, xfs and overlay. Note that xfs online scrub
will be run by default after each test if there's an executable xfs_scrub
binary and kernel supports it, you don't have to set TEST_XFS_SCRUB=1 now.
New failures I've noticed in this update:
- btrfs/15[23] fail with current v4.14-rc7 kernel
Thanks,
Eryu
The new head of the master branch is commit:
68d2ebf90d94 xfs/020: check that we have enough space to write out a huge fs
New commits:
Amir Goldstein (1):
[5f49f15cf496] overlay: test creating lower hardlinks for copied up files
Darrick J. Wong (12):
[5cd65cb761d9] common/xfs: refactor xfs_scrub presence testing
[ced4117fb924] common/xfs: standardize the xfs_scrub output that gets recorded to $seqres.full
[a6ce8c2c9eb2] fstests: add module reloading helpers
[8d021705b5cd] common/xfs: remove inode-paths cruft
[0862b1d8b6a7] xfs/333: fix errors with new inode pointer verifiers
[36ea1258684b] common/rc: force mkfs for xfs in _mkfs_dev
[a9006d7c6227] generic/459: explicitly require thin_check
[8b190e89fde1] xfs/122: add inode log formats
[b934adce93a2] xfs: filter and record the unknown block state messages
[14d062b1e9a8] xfs/013: don't fail because cp ran out of space
[2d54a4cda310] generic: test IO at maximum file offset
[68d2ebf90d94] xfs/020: check that we have enough space to write out a huge fs
Justin Maggard (2):
[93dcb9861eea] btrfs: test if receive with qgroups corrupts metadata
[230efa52a4c2] btrfs: test for qgroup reservation leaks with prealloc
Code Diffstat:
README | 6 +--
common/btrfs | 12 -----
common/config | 1 +
common/module | 99 ++++++++++++++++++++++++++++++++++++
common/overlay | 1 +
common/rc | 18 ++-----
common/repair | 9 ++++
common/xfs | 53 ++++++++++++++-----
tests/btrfs/124 | 9 ++--
tests/btrfs/125 | 9 ++--
tests/btrfs/152 | 102 +++++++++++++++++++++++++++++++++++++
tests/btrfs/152.out | 13 +++++
tests/btrfs/153 | 72 ++++++++++++++++++++++++++
tests/btrfs/153.out | 2 +
tests/btrfs/group | 2 +
tests/generic/453 | 12 +----
tests/generic/454 | 12 +----
tests/generic/459 | 1 +
tests/generic/466 | 102 +++++++++++++++++++++++++++++++++++++
tests/generic/466.out | 2 +
tests/generic/group | 1 +
tests/overlay/042 | 138 ++++++++++++++++++++++++++++++++++++++++++++++++++
tests/overlay/042.out | 2 +
tests/overlay/group | 1 +
tests/xfs/010 | 2 +-
tests/xfs/013 | 11 ++--
tests/xfs/020 | 4 ++
tests/xfs/030 | 2 +-
tests/xfs/122.out | 2 +
tests/xfs/333 | 18 ++-----
tests/xfs/333.out | 7 +--
31 files changed, 629 insertions(+), 96 deletions(-)
--
Eryu Guan
eguan@redhat.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
reply other threads:[~2017-11-05 8:31 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=59fecc65.019c620a.2c7a4.e533@mx.google.com \
--to=guaneryu@gmail.com \
--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