All of lore.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 55f4ad17f3e4
Date: Sun, 28 Apr 2019 23:19:25 +0800	[thread overview]
Message-ID: <5cc5c488.1c69fb81.2e76.c686@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1342 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. The new btrfs test (btrfs/187) currently fails on
latest Kernel (v5.1-rc6). Apart from that, other commits are mostly minor bug
fixes and improvements.

Thanks,
Eryu

The new head of the master branch is commit:

55f4ad17f3e4 generic/487: reorder logdev detection after filesystem detection

New commits:

Darrick J. Wong (1):
      [26a0e060e431] misc: xfs_fsop_geom_t -> struct xfs_fsop_geom

David Sterba (1):
      [55f4ad17f3e4] generic/487: reorder logdev detection after filesystem detection

Filipe Manana (2):
      [8afebc02235e] btrfs: stress send with deduplication and balance running in parallel
      [195a650883b0] btrfs: fix filtering of scratch device in test case 048


Code Diffstat:

 dmapi/src/suite1/cmd/make_rt_sparse.c |   2 +-
 ltp/fsstress.c                        |   2 +-
 tests/btrfs/048                       |  10 +-
 tests/btrfs/048.out                   |  10 +-
 tests/btrfs/187                       | 226 ++++++++++++++++++++++++++++++++++
 tests/btrfs/187.out                   |   3 +
 tests/btrfs/group                     |   1 +
 tests/generic/487                     |   2 +-
 8 files changed, 243 insertions(+), 13 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2019-04-28 15:19 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=5cc5c488.1c69fb81.2e76.c686@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.