From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to 00e3549c659c
Date: Sun, 06 May 2018 22:13:39 +0800 [thread overview]
Message-ID: <5aef0d98.4e21620a.be12e.c614@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3291 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. Notably, the default behavior of a pure './check' has
been changed in this update, it now runs tests only in 'auto' group by default,
instead of all tests. But you could still use './check -g auto' as usual to run
'auto' tests.
There're also two new generic tests and some random test fixes & improvements.
The two new tests both should not fail on latest Linus tree (v4.17-rc3+).
Thanks,
Eryu
The new head of the master branch is commit:
00e3549c659c xfs/132: remove duplicate test
New commits:
Amir Goldstein (1):
[00e3549c659c] xfs/132: remove duplicate test
Darrick J. Wong (7):
[38cdd5be450e] generic: test XATTR_REPLACE doesn't take the fs down
[524a7061a1f4] generic/45[34]: add unicode directional override checks
[2daf94ec9143] generic/45[34]: check unicode names only if xfs_scrub linked against libicu
[2426366fc31f] generic/45[34]: test unicode confusables
[d2603933ebc5] generic/453: test creation of malicious directory entries
[e2fd1a080ece] xfs/422: add fsstress to the freeze-and-rmap-repair race test
[0828657542ea] xfs: fix blocktrash fuzzers
Dave Chinner (2):
[b4c032f1bd30] check: run auto test group by default
[60af5cc1e243] README: document the new default run mode
Eric Biggers (1):
[d0f42b253010] generic: test exceeding max file size via INSERT_RANGE
Jeff Layton (1):
[0c2896508f44] src/fsync-err: don't truncate files on second open
Theodore Ts'o (1):
[da7916f72206] build: Use the original install-sh file from SGI
Code Diffstat:
.gitignore | 1 +
Makefile | 1 +
README | 38 +++---
check | 34 +++--
include/install-sh | 351 ++++++++++++++++++++++++++++++++++++++++++++++++
src/Makefile | 3 +-
src/attr_replace_test.c | 67 +++++++++
src/fsync-err.c | 8 +-
tests/generic/453 | 100 +++++++++++++-
tests/generic/454 | 66 ++++++++-
tests/generic/485 | 115 ++++++++++++++++
tests/generic/485.out | 4 +
tests/generic/486 | 71 ++++++++++
tests/generic/486.out | 2 +
tests/generic/group | 2 +
tests/xfs/086 | 15 ++-
tests/xfs/087 | 19 +--
tests/xfs/088 | 15 ++-
tests/xfs/089 | 15 ++-
tests/xfs/091 | 15 ++-
tests/xfs/093 | 19 +--
tests/xfs/097 | 19 +--
tests/xfs/099 | 11 +-
tests/xfs/100 | 11 +-
tests/xfs/101 | 11 +-
tests/xfs/102 | 11 +-
tests/xfs/105 | 11 +-
tests/xfs/112 | 11 +-
tests/xfs/113 | 11 +-
tests/xfs/117 | 25 ++--
tests/xfs/120 | 17 +--
tests/xfs/123 | 7 +-
tests/xfs/124 | 9 +-
tests/xfs/125 | 9 +-
tests/xfs/126 | 9 +-
tests/xfs/132 | 126 -----------------
tests/xfs/132.out | 12 --
tests/xfs/235 | 11 +-
tests/xfs/337 | 11 +-
tests/xfs/422 | 18 ++-
tests/xfs/group | 1 -
41 files changed, 996 insertions(+), 316 deletions(-)
--
Eryu Guan
guaneryu@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2018-05-06 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 14:13 Eryu Guan [this message]
2018-05-07 4:22 ` [ANNOUNCE] fstests: master branch updated to 00e3549c659c Eryu Guan
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=5aef0d98.4e21620a.be12e.c614@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