public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] xfstests: master branch updated to 6721ab0
Date: Wed, 27 Jul 2016 14:20:07 +1000	[thread overview]
Message-ID: <20160727042007.GI12670@dastard> (raw)

[-- Attachment #1: Type: text/plain, Size: 3323 bytes --]

Hi folks,

The xfstests repositories at:

	git://oss.sgi.com/xfs/cmds/xfstests
	git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git

have just been updated. The change summary from Eryu's pull request:

	This update contains:

	o Improvements in extended test names handling
	o The first test with an extended name (xfs/191-input-validation)
	o New test cases for xfs and btrfs
	o Other bug fixes and improvements

The full list of changes merged is below.

-Dave.

Patches often get missed, so please check if your outstanding
patches were in this update. If they have not been in this update,
please resubmit them to fstests@vger.kernel.org so they can be
picked up in the next update.

The new head of the master branch is commit:

6721ab0 generic/235: Fix false failures for some quota formats

New Commits:

Christoph Hellwig (1):
      [b62a0b3] generic/120: requires working *atime mount options

Eric Sandeen (1):
      [cf94bc8] generic/075,112: fix up fsx error handling

Eryu Guan (2):
      [58bff72] common/rc: avoid mkfs option conflicts in _scratch_mkfs_xfs_supported
      [a4cafa0] xfs: fix wrong seq order in group file

Jan Kara (3):
      [9b06a9f] generic/294: Filter backquotes from mknod error output
      [e1f9441] common/filter: Improve xfs_io filter
      [6721ab0] generic/235: Fix false failures for some quota formats

Jan Tulak (4):
      [cb15a45] build: Fix installation for extended names
      [1fd02fd] check: fix extended names handling
      [27daf0c] check: remove unused variable
      [9a8bdd8] xfs: Add mkfs input validation tests

Qu Wenruo (2):
      [a4f0a9b] btrfs: send on fully deduped file
      [fc2b488] btrfs: Update quick and auto tag for btrfs group

Xiao Yang (1):
      [b659460] xfs/083: disable dmesg check


Code Diffstat:

 check                              |  26 ++--
 common/filter                      |   6 +-
 common/rc                          |  11 +-
 include/buildrules                 |  32 ++++
 tests/btrfs/130                    |  89 +++++++++++
 tests/btrfs/130.out                |   3 +
 tests/btrfs/Makefile               |   4 +-
 tests/btrfs/group                  |   9 +-
 tests/cifs/Makefile                |   4 +-
 tests/ext4/Makefile                |   4 +-
 tests/f2fs/Makefile                |   4 +-
 tests/generic/075                  |   4 +-
 tests/generic/112                  |   2 +-
 tests/generic/120                  |   2 +
 tests/generic/235                  |   9 +-
 tests/generic/235.out              |   8 -
 tests/generic/Makefile             |   4 +-
 tests/overlay/Makefile             |   4 +-
 tests/shared/Makefile              |   4 +-
 tests/udf/Makefile                 |   4 +-
 tests/xfs/083                      |   4 +
 tests/xfs/191-input-validation     | 338 ++++++++++++++++++++++++++++++++++++++++
 tests/xfs/191-input-validation.out |   2 +
 tests/xfs/Makefile                 |   4 +-
 tests/xfs/group                    |   3 +-
 25 files changed, 533 insertions(+), 51 deletions(-)
 create mode 100755 tests/btrfs/130
 create mode 100644 tests/btrfs/130.out
 create mode 100755 tests/xfs/191-input-validation
 create mode 100644 tests/xfs/191-input-validation.out
-- 
Dave Chinner
david@fromorbit.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2016-07-27  4:20 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=20160727042007.GI12670@dastard \
    --to=david@fromorbit.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