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 9bcb266cd778
Date: Sun, 18 Jun 2017 20:57:32 +0800	[thread overview]
Message-ID: <594678c1.816c630a.b0b23.ee2f@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1393 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 relatively small update, which has new tests
for fscrypt and btrfs, and minor fixes for UDF.

New failure I've noticed in this update:
- btrfs/145 fails with latest 4.12-rc5 Linus tree

Thanks,
Eryu

The new head of the master branch is commit:

9bcb266cd778 generic/397: be compatible with ignored SIGPIPE

New commits:

Eric Biggers (2):
      [7e442cf0cf95] generic: test for buggy fscrypt context consistency check
      [9bcb266cd778] generic/397: be compatible with ignored SIGPIPE

Filipe Manana (1):
      [31e424c4aa3c] btrfs: incremental send after renaming a file and a directory

Jan Kara (2):
      [0a2d8332195a] generic/360: Create symlink with valid path
      [fabaef26ad59] common: UDF does not support journalling


Code Diffstat:

 common/rc             |   2 +-
 tests/btrfs/145       | 130 ++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/btrfs/145.out   |   6 +++
 tests/btrfs/group     |   1 +
 tests/generic/360     |   4 +-
 tests/generic/360.out |   2 +-
 tests/generic/397     |   2 +-
 tests/generic/440     | 114 +++++++++++++++++++++++++++++++++++++++++++
 tests/generic/440.out |  13 +++++
 tests/generic/group   |   1 +
 10 files changed, 271 insertions(+), 4 deletions(-)
--
Eryu Guan
eguan@redhat.com

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

                 reply	other threads:[~2017-06-18 12:57 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=594678c1.816c630a.b0b23.ee2f@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