From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to f3a1213c2494
Date: Sun, 06 Jan 2019 22:56:48 +0800 [thread overview]
Message-ID: <5c321737.1c69fb81.b9424.ce58@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1410 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. This is a bugfix-only update, and notably we reverted
the RESULT_BASE fix in kmemleak support (sorry for suggesting a wrong fix), it
turns that it's the kmemleak infrastracture that needs to be fixed (I'll look
into it next week).
Thanks,
Eryu
The new head of the master branch is commit:
f3a1213c2494 Revert "common/config: create $RESULT_BASE before dumping kmemleak leaks"
New commits:
Hou Tao (3):
[46c1a950e375] xfs: only set XFS_MKFS_HAS_NO_META_SUPPORT for XFS
[2408f208c106] fsx: check ENOSYS in test_copy_range() & test_fallocate()
[e18876187ce7] generic/131: wait until the server is ready or timeout
Nikolay Borisov (1):
[f3a1213c2494] Revert "common/config: create $RESULT_BASE before dumping kmemleak leaks"
Zorro Lang (2):
[6dbca6feb9ff] generic/474: shift target directory to a sub-dir of SCRATCH_MNT
[b0c8dbccf438] xfs/139-140: skip testing on large scratch dev
Code Diffstat:
check | 7 +++++++
common/config | 23 ++++++++++-------------
ltp/fsx.c | 5 +++--
tests/generic/131 | 21 ++++++++++++++++++---
tests/generic/474 | 12 ++++++++----
tests/xfs/139 | 3 +++
tests/xfs/140 | 3 +++
7 files changed, 52 insertions(+), 22 deletions(-)
--
Eryu Guan
guaneryu@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2019-01-06 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 14:56 Eryu Guan [this message]
2019-01-06 18:10 ` [ANNOUNCE] fstests: master branch updated to f3a1213c2494 Darrick J. Wong
2019-01-07 8:47 ` 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=5c321737.1c69fb81.b9424.ce58@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.