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 67a76593ba2e
Date: Mon, 25 Nov 2019 00:28:47 +0800	[thread overview]
Message-ID: <5ddaafc5.1c69fb81.7e284.ad99@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2095 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 is basically a bugfix update, the only new test is
btrfs/201, which currently fails with latest upstream kernel.

My apologies that I've been busy with other work recently and have limit time
reviewing patches, so there was no update last week, and I still have some
review backlogs to catch up. I'm really appreciated that if you could help
review the pending patches, especially the following patches:

- fscrypt patches (RFC), from Eric Biggers
- btrfs subvol & snapshot support to fsstress, from Josef Bacik
- ext4 tests ported from LTP, from Yong Sun

Thanks,
Eryu

The new head of the master branch is commit:

67a76593ba2e btrfs: test fsync after hole punching when using the no-holes feature

New commits:

Amir Goldstein (1):
      [acb2ba78a378] overlay: support timestamp range check

Filipe Manana (1):
      [67a76593ba2e] btrfs: test fsync after hole punching when using the no-holes feature

Jan Kara (2):
      [e0884798713c] generic/050: Handle xfs quota special case with different output
      [bb7c6d6172d3] generic/050: Consistently remove traling dot from umount output

Naohiro Aota (1):
      [3414cae6d231] btrfs/085: check flakey device instead of backend device

Xiaoli Feng (1):
      [86216d73ef61] ext4/031: use _try_scratch_mount instead of _scratch_mount

Zorro Lang (1):
      [f3e465ae9136] generic/563: fix the wrong case number in golden image


Code Diffstat:

 common/rc                      |  10 ++-
 tests/btrfs/085                |   2 +-
 tests/btrfs/201                | 190 +++++++++++++++++++++++++++++++++++++++++
 tests/btrfs/201.out            |  24 ++++++
 tests/btrfs/group              |   1 +
 tests/ext4/031                 |   2 +-
 tests/generic/050              |  62 ++++----------
 tests/generic/050.cfg          |   1 +
 tests/generic/050.out.xfsquota |  25 ++++++
 tests/generic/563.out          |   2 +-
 10 files changed, 270 insertions(+), 49 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

             reply	other threads:[~2019-11-24 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-24 16:28 Eryu Guan [this message]
2019-11-24 16:53 ` [ANNOUNCE] fstests: master branch updated to 67a76593ba2e Amir Goldstein

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=5ddaafc5.1c69fb81.7e284.ad99@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).