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 60d9b58605fd
Date: Sun, 08 Nov 2020 18:10:23 +0800	[thread overview]
Message-ID: <5fa7c412.1c69fb81.7495b.02d9@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2068 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 contains various random bug fixes, most of
them are from Darrick J. Wong. The patch from Eric Biggers that adds Makefile
for ceph tests indicates I need to improve my release testing, adding
"make install" test.

Also, there's one new test that checks st_blocks after writing into a hole by
mmap write, and it currently fails with btrfs.

Thanks,
Eryu

The new head of the master branch is commit:

60d9b58605fd xfs/030: hide the btree levels check errors

New commits:

Darrick J. Wong (6):
      [9062902a5981] xfs/520: disable external devices
      [826016f2261e] xfs/341: fix test when rextsize > 1
      [b951bb5cef51] various: replace _get_block_size with _get_file_block_size when needed
      [f3d639b1cc72] xfs/327: fix inode reflink flag checking
      [e97f96e55f2d] xfs/27[26]: force realtime on or off as needed
      [60d9b58605fd] xfs/030: hide the btree levels check errors

Eric Biggers (1):
      [1de2b58b8e29] tests/ceph: add Makefile

Filipe Manana (1):
      [043e5bb164a6] generic: test number of blocks used by a file after mwrite into a hole

Jeff Layton (1):
      [e71ecb8f1c1e] src/append_reader.c: print more info when it reads bad data

Josef Bacik (1):
      [a0bcdb6cbf42] btrfs/220: fix how we tests for mount options


Code Diffstat:

 common/repair         |   1 +
 src/append_reader.c   |   2 +-
 tests/btrfs/220       | 124 +++++++++++++++++++++++++++++++-------------------
 tests/ceph/Makefile   |  18 ++++++++
 tests/generic/614     |  50 ++++++++++++++++++++
 tests/generic/614.out |   2 +
 tests/generic/group   |   1 +
 tests/xfs/030         |   1 +
 tests/xfs/272         |   3 ++
 tests/xfs/276         |   8 +++-
 tests/xfs/327         |  18 +++++++-
 tests/xfs/327.out     |  13 +++---
 tests/xfs/328         |   2 +-
 tests/xfs/341         |   8 ++--
 tests/xfs/520         |   3 ++
 15 files changed, 193 insertions(+), 61 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2020-11-08 10:10 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=5fa7c412.1c69fb81.7495b.02d9@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