From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to 034744b82385
Date: Sat, 10 Jun 2017 23:45:36 +0800 [thread overview]
Message-ID: <593c1423.4405630a.41f5.21dc@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1866 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. fstests gains ubifs support in this update, many thanks
to David Oberhollenzer! Besides that, there're two new btrfs tests and a minor
bug fix added in this update.
New failures I've noticed:
- btrfs/144 fails on latest 4.12-rc4 kernel
Thanks,
Eryu
The new head of the master branch is commit:
034744b82385 btrfs: test incremental send after renaming and linking file
New commits:
David Oberhollenzer (4):
[d4c9003b5294] common/rc: Add tests for character devices
[cc34c5f81f26] fstests: Add support for UBIFS
[62de87749aeb] generic/398: Accept failing with EPERM in addition to ENOKEY for rename without key
[1cc2487f501f] fstests: Fix block device requirements and manual scratch mounts
Filipe Manana (1):
[034744b82385] btrfs: test incremental send after renaming and linking file
Nikolay Borisov (1):
[7b6729e9ab5a] generic/019: Silence possible kill failure
Omar Sandoval (1):
[ff1f614f3373] btrfs: test Btrfs delalloc accounting overflow
Code Diffstat:
check | 2 +
common/config | 17 ++++++--
common/encrypt | 4 ++
common/rc | 68 +++++++++++++++++++++++++++++
tests/btrfs/010 | 75 ++++++++++++++++++++++++++++++++
tests/btrfs/010.out | 2 +
tests/btrfs/144 | 118 ++++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/144.out | 6 +++
tests/btrfs/group | 2 +
tests/generic/019 | 2 +-
tests/generic/076 | 2 +-
tests/generic/398 | 10 ++++-
tests/generic/398.out | 4 +-
tests/generic/409 | 8 ++--
tests/generic/410 | 8 ++--
tests/generic/411 | 10 ++---
16 files changed, 316 insertions(+), 22 deletions(-)
--
Eryu Guan
eguan@redhat.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
reply other threads:[~2017-06-10 15:45 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=593c1423.4405630a.41f5.21dc@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