All of lore.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 777e1d628029
Date: Sun, 14 May 2017 17:28:28 +0800	[thread overview]
Message-ID: <5918233f.45a6620a.43941.5330@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2731 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. There're five new generic tests for copy_file_range(2)
syscall added in this update. Many thanks to Anna Schumaker, also thank Darrick
for reviewing these new tests! Besides that, there're improvements to
set_prog_path function to make things run a bit faster, more improvements to
overlayfs consistent inode test, and a bug fix to seek_sanity_test found in
cephfs testing.

New failures I've noticed in this update:
- copy_file_range(2) tests generic/430, generic/433 and generic/434 fail when
  testing cifs against a Linux samba server, tests return EIO if offset of
  source file is or greater than file size.

Thanks,
Eryu

The new head of the master branch is commit:

777e1d628029 overlay/017: test consistent st_ino/d_ino for hardlinks

New commits:

Amir Goldstein (3):
      [0b7318100594] src/t_dir_type: support filtering by inode number
      [a19298e36317] overlay/017: use t_dir_type to find file by d_ino
      [777e1d628029] overlay/017: test consistent st_ino/d_ino for hardlinks

Anna Schumaker (5):
      [330ba8b3c36a] generic: Add copy to new file test
      [7dada91d00b5] generic: Add small copies to new file test
      [cd3908f4dc07] generic: Add copy test that overwrites data
      [e52ffc092397] generic: Add a copy test for overwriting small amounts of data
      [dabd808a5233] generic: Add a copy test for invalid input

Eric Biggers (2):
      [7b1ae2457c81] common/config: make set_prog_path() accept one argument only
      [904a46958ca0] common/config: implement set_prog_path() using 'type -P'

Luis Henriques (1):
      [763008fd8800] src/seek_sanity_test: ensure file size is big enough


Code Diffstat:

 common/config              |  20 +--------
 common/rc                  |   6 +++
 doc/auxiliary-programs.txt |   7 ++++
 src/seek_sanity_test.c     |   6 +--
 src/t_dir_type.c           |  11 +++--
 tests/generic/430          | 102 +++++++++++++++++++++++++++++++++++++++++++++
 tests/generic/430.out      |  25 +++++++++++
 tests/generic/431          |  83 ++++++++++++++++++++++++++++++++++++
 tests/generic/431.out      |  15 +++++++
 tests/generic/432          | 100 ++++++++++++++++++++++++++++++++++++++++++++
 tests/generic/432.out      |  17 ++++++++
 tests/generic/433          |  87 ++++++++++++++++++++++++++++++++++++++
 tests/generic/433.out      |  17 ++++++++
 tests/generic/434          |  79 +++++++++++++++++++++++++++++++++++
 tests/generic/434.out      |  14 +++++++
 tests/generic/group        |   5 +++
 tests/overlay/017          |   9 ++--
 17 files changed, 575 insertions(+), 28 deletions(-)
--
Eryu Guan
eguan@redhat.com

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

                 reply	other threads:[~2017-05-14  9:28 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=5918233f.45a6620a.43941.5330@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.