fstests.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to 2806589445b8
Date: Mon, 10 Feb 2020 00:03:53 +0800	[thread overview]
Message-ID: <5e402d6e.1c69fb81.a5f7a.9694@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2133 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 mainly pulls in the patches that have been
reviewed by someone, which accelerates the review & merge process a lot, many
thanks to the contributors as well as the reviewers!

Though there're two new btrfs tests and one new test case in generic/527, but
there should be no new failures if you're testing with latest Linus tree.

Thanks,
Eryu

The new head of the master branch is commit:

2806589445b8 btrfs/022: Add debug output

New commits:

Darrick J. Wong (4):
      [1d22275b06aa] xfs/449: filter out "Discarding..." from output
      [13a86fa73d52] xfs/020: fix truncation test
      [1f3f20c52f0a] xfs/117: fix inode corruption loop
      [05730e20c354] fsx: support 64-bit operation counts

Eric Biggers (1):
      [1c5c2aa7f6da] generic/581: try to avoid flakiness in keys quota test

Filipe Manana (2):
      [c0679253bc14] generic/527: add additional test including a file with a hardlink
      [8a861b8faf1f] btrfs: add test for incremental send for file with shared extents

Josef Bacik (1):
      [2d4500367c5e] btrfs: add a test for the btrfs file extent gap issue

Qu Wenruo (3):
      [f41020d7f026] btrfs: Use word mathcing for _btrfs_get_subvolid()
      [9e2be2b1330b] btrfs/022: Match qgroup id more correctly
      [2806589445b8] btrfs/022: Add debug output


Code Diffstat:

 common/btrfs          |   2 +-
 ltp/fsx.c             |  54 ++++++++++++++-------------
 tests/btrfs/022       |  19 +++++++---
 tests/btrfs/172       |  76 ++++++++++++++++++++++++++++++++++++++
 tests/btrfs/172.out   |   3 ++
 tests/btrfs/203       | 100 ++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/btrfs/203.out   |  25 +++++++++++++
 tests/btrfs/group     |   2 +
 tests/generic/527     |  26 +++++++++++++
 tests/generic/527.out |   4 ++
 tests/generic/581     |  29 +++++++++++----
 tests/xfs/020         |   4 +-
 tests/xfs/117         |   2 +-
 tests/xfs/449         |   2 +-
 14 files changed, 304 insertions(+), 44 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2020-02-09 16:04 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=5e402d6e.1c69fb81.a5f7a.9694@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;
as well as URLs for NNTP newsgroup(s).