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 94c19d60a2ce
Date: Sun, 06 Oct 2019 23:07:57 +0800	[thread overview]
Message-ID: <5d9a0354.1c69fb81.98520.97e7@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2698 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 a relatively big update, which contains 11 new
patches, includes 5 new test cases and other random bug fixes.

New failures I've noticed in this update:
- btrfs/194 and btrfs/195 currently fail with latest kernel on btrfs
- generic/568 fails when testing on XFS
- generic/569 & generic/570 fail on all filesystems that support swap file

There're still two big patchset that need review (lease tests from Ira Weiny
and fs-verity tests from Eric Biggers), hopefully I'll review them in next
week.

Thanks,
Eryu

The new head of the master branch is commit:

94c19d60a2ce btrfs: test balance profile convert functionality

New commits:

Chao Yu (1):
      [f45d9b2fecd1] generic/493: add missing dedupe group

Darrick J. Wong (1):
      [db8feee94964] generic: check that we can't write to swap files

Filipe Manana (1):
      [b727d8af324c] btrfs/036: fix sporadic failures when unmounting scratch filesystem

Max Reitz (1):
      [c599af2ca621] generic: fallocate two bytes at block boundary

Nikolay Borisov (2):
      [74f448265ac2] common/rc: Remove special handing of 'dup' argument for btrfs
      [94c19d60a2ce] btrfs: test balance profile convert functionality

Po-Hsu Lin (1):
      [771f879c1a06] check: convert spaces to tabs in help msg

Qu Wenruo (2):
      [fa85aa649760] btrfs/011: Fill the fs to ensure we have enough data for dev-replace
      [c0eab1ea2317] btrfs: Add regression test to check if btrfs can handle high devid

Zhihao Cheng (1):
      [4cec72bb1691] overlay: Enable character device to be the base fs partition

Zorro Lang (1):
      [7ddb754f15ce] common/xfs: wipe the XFS superblock of each AGs


Code Diffstat:

 check                 |  12 ++---
 common/config         |   6 +--
 common/rc             |  18 ++++---
 common/xfs            |  40 +++++++++++++++
 src/swapon.c          | 135 ++++++++++++++++++++++++++++++++++++++++++++++++--
 tests/btrfs/011       |  42 +++++++++++++---
 tests/btrfs/036       |   7 +++
 tests/btrfs/194       |  86 ++++++++++++++++++++++++++++++++
 tests/btrfs/194.out   |   2 +
 tests/btrfs/195       |  84 +++++++++++++++++++++++++++++++
 tests/btrfs/195.out   |   2 +
 tests/btrfs/group     |   2 +
 tests/generic/568     |  60 ++++++++++++++++++++++
 tests/generic/568.out |   4 ++
 tests/generic/569     |  70 ++++++++++++++++++++++++++
 tests/generic/569.out |  14 ++++++
 tests/generic/570     |  56 +++++++++++++++++++++
 tests/generic/570.out |  12 +++++
 tests/generic/group   |   5 +-
 19 files changed, 628 insertions(+), 29 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2019-10-06 15:08 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=5d9a0354.1c69fb81.98520.97e7@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