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 69c6da403991
Date: Mon, 22 Jul 2019 01:01:25 +0800	[thread overview]
Message-ID: <5d349a6a.1c69fb81.84578.1d86@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2157 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 update pulls in the remaining copy_file_range
tests from Amir and Dave, a new btrfs regression tests and moves shared/011
into generic.

The two new copy_file_range tests should not fail if you're testing with latest
Linus tree (v5.2.0+), but you may still see btrfs/191 failure.

I'm sorry that I still don't have much time reviewing the fsverity patches, but
that doesn't mean I forget about it :)

Thanks,
Eryu

The new head of the master branch is commit:

69c6da403991 generic: cross-device copy_file_range test

New commits:

Amir Goldstein (3):
      [3996a90a471f] common/rc: check support for xfs_io copy_range -f N
      [f60eeb9a2197] generic: copy_file_range bounds test
      [69c6da403991] generic: cross-device copy_file_range test

Chao Yu (1):
      [3bfeb4d53f5e] common/rc: set max label length for f2fs

Christoph Hellwig (3):
      [e678a7cc9ca6] common/cgroup2: better error message if cgroup2 fs is not mounted
      [02994bdad6c7] shared/011: run for all block device based file systems
      [1a4485f2fafe] shared/011: move to generic/

Filipe Manana (1):
      [901c4e5d19b0] btrfs: test incremental send after deduplication on both snapshots


Code Diffstat:

 common/cgroup2                            |   5 ++
 common/rc                                 |  12 ++-
 tests/btrfs/191                           | 110 ++++++++++++++++++++++++
 tests/btrfs/191.out                       |  19 +++++
 tests/btrfs/group                         |   1 +
 tests/{shared/011 => generic/563}         |   5 +-
 tests/{shared/011.out => generic/563.out} |   0
 tests/generic/564                         | 134 ++++++++++++++++++++++++++++++
 tests/generic/564.out                     |  37 +++++++++
 tests/generic/565                         |  64 ++++++++++++++
 tests/generic/565.out                     |   4 +
 tests/generic/group                       |   3 +
 tests/shared/group                        |   1 -
 13 files changed, 392 insertions(+), 3 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2019-07-21 17:01 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=5d349a6a.1c69fb81.84578.1d86@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