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 cfea24abcf9a
Date: Mon, 31 Aug 2020 00:31:21 +0800	[thread overview]
Message-ID: <5f4bd45c.1c69fb81.f3fe2.2df1@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1280 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 contains btrfs new test and fixes.
And you may see the new btrfs/218 test fail with latest v5.9-rc2 kernel.

Thanks,
Eryu

The new head of the master branch is commit:

cfea24abcf9a generic/574: fix sporadic failure with test_dummy_encryption

New commits:

Eric Biggers (1):
      [cfea24abcf9a] generic/574: fix sporadic failure with test_dummy_encryption

Josef Bacik (1):
      [25824c270360] btrfs: add a test for btrfs seed device stats

Nikolay Borisov (3):
      [7b82ef0ff757] btrfs/024: Remove no longer valid test
      [473d0e1740ca] btrfs/205: Ignore output of chattr command
      [b9d1dcd13516] common/config: Allow sections names to contain hyphen


Code Diffstat:

 common/config         |  2 +-
 tests/btrfs/024       |  7 -----
 tests/btrfs/024.out   |  3 ---
 tests/btrfs/205       |  2 +-
 tests/btrfs/218       | 73 +++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/btrfs/218.out   | 25 ++++++++++++++++++
 tests/btrfs/group     |  1 +
 tests/generic/574     | 11 +++++---
 tests/generic/574.out |  6 ++---
 9 files changed, 112 insertions(+), 18 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

             reply	other threads:[~2020-08-30 16:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-30 16:31 Eryu Guan [this message]
2020-08-31  1:06 ` [ANNOUNCE] fstests: master branch updated to cfea24abcf9a Yang Xu

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=5f4bd45c.1c69fb81.f3fe2.2df1@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).