From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to 545e7ca67bea
Date: Sun, 25 Mar 2018 20:32:12 +0800 [thread overview]
Message-ID: <5ab796d3.0e44620a.96f0b.e812@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1385 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. Jeff Mahoney fixed &
cleaned up libgdbm detection, Darrick J. Wong fixed various problems in
xfs_scrub test infrastructure, and Xiong Zhou fixed a potential infinite loop
in OFD lock test. There should be no new failures introduced.
Thanks,
Eryu
The new head of the master branch is commit:
545e7ca67bea generic/478: fix potential test blocking
New commits:
Darrick J. Wong (2):
[064c61898963] common/xfs: don't call xfs_scrub on a block device
[8aa212310d62] common/xfs: fix various problems with _supports_xfs_scrub
Jeff Mahoney (4):
[81d27bdc0a10] build: remove dead AC_PACKAGE_WANT_NDBM macro
[156dafb888a6] build: AC_PACKAGE_WANT_GDBM, fall back to compat if libgdbm detection fails
[3a670ba14256] build: clean up AC_PACKAGE_WANT_GDBM
[581862bdc023] build: fix <ndbm.h> detection in AC_PACKAGE_WANT_GDBM
Xiong Zhou (1):
[545e7ca67bea] generic/478: fix potential test blocking
Code Diffstat:
common/xfs | 10 +++--
m4/package_gdbmdev.m4 | 104 ++++++++++++++++++++++----------------------------
src/dbtest.c | 3 --
src/t_ofd_locks.c | 16 +++++---
4 files changed, 63 insertions(+), 70 deletions(-)
--
Eryu Guan
guaneryu@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
reply other threads:[~2018-03-25 12:32 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=5ab796d3.0e44620a.96f0b.e812@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