public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to 16985be90e5e
Date: Sun, 28 May 2017 16:48:51 +0800	[thread overview]
Message-ID: <592a8ef9.426b630a.63702.84dd@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2753 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. The first NFS specific test has been added in this
update, hope that we'll have more NFS tests. Another major change is that
OpenSSL is not required anymore for building fstests. Other changes are all
minor bug fixes and build warning fixes.

There should be no new failures introduced in this update.

Thanks,
Eryu

The new head of the master branch is commit:

16985be90e5e nfs: test nfs4_getfacl near page size ACL from server

New commits:

Eryu Guan (1):
      [16985be90e5e] nfs: test nfs4_getfacl near page size ACL from server

Luis Henriques (1):
      [890f2b5ae24f] src/seek_sanity_test: fix test15 SEEK_HOLE expected results

Nikolay Borisov (2):
      [2d77f8580636] xfs/293: Make 'man' hard requirement
      [c51ab0a8502e] generic/108: Fix return value check from _get_scsi_debug_dev

Richard Weinberger (1):
      [b14d1bb8b3f6] src/stat_test: Fix stx_attributes check

Theodore Ts'o (2):
      [7ee1b53d77e5] src: fix compiler warnings
      [d0ef33ce972d] build: Stop relying on OpenSSL

Zorro Lang (2):
      [1262cc70fa42] xfs/196: fallback to fail_writes for old kernel
      [ce16ed94a8d9] xfs/288: filter out extra mkfs warning


Code Diffstat:

 README                                   |   2 +-
 common/config                            |   3 +
 common/nfs                               |  35 ++++
 common/rc                                |   1 +
 configure.ac                             |   1 -
 include/builddefs.in                     |   1 -
 m4/package_ssldev.m4                     |   4 -
 src/Makefile                             |  18 +-
 src/aio-dio-regress/aio-dio-eof-race.c   |   3 +-
 src/aio-dio-regress/aio-dio-fcntl-race.c |  32 +++-
 src/dio-invalidate-cache.c               |   6 +-
 src/fssum.c                              |   6 +-
 src/holetest.c                           |   8 +-
 src/md5.c                                | 291 +++++++++++++++++++++++++++++++
 src/md5.h                                |  45 +++++
 src/seek_sanity_test.c                   |   5 +-
 src/stat_test.c                          |   4 +-
 src/t_rename_overwrite.c                 |   3 +-
 tests/generic/108                        |   2 +-
 tests/nfs/001                            |  77 ++++++++
 tests/nfs/001.out                        |   2 +
 tests/nfs/Makefile                       |  20 +++
 tests/nfs/group                          |   6 +
 tests/xfs/196                            |  16 +-
 tests/xfs/288                            |   2 +-
 tests/xfs/293                            |   6 +-
 26 files changed, 549 insertions(+), 50 deletions(-)
--
Eryu Guan
eguan@redhat.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

                 reply	other threads:[~2017-05-28  8:48 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=592a8ef9.426b630a.63702.84dd@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