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 1cb1f7eccf98
Date: Mon, 25 May 2020 01:05:57 +0800	[thread overview]
Message-ID: <5ecaa97c.1c69fb81.2e77c.a238@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2790 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. There're 8 new tests added in this update, including 2
generic tests, 2 btrfs tests and 4 xfs tests, and all of them should pass with
v5.7-rc6 kernel. The other commits are random bug fixes, as usual.

Many thanks to those who helped review patches!

Thanks,
Eryu

The new head of the master branch is commit:

1cb1f7eccf98 overlay/031: fix failure with whiteout inode sharing

New commits:

Amir Goldstein (1):
      [1cb1f7eccf98] overlay/031: fix failure with whiteout inode sharing

Darrick J. Wong (4):
      [06fd8dbbfe31] xfs: test that reflink forces the log if mounted with wsync
      [88e954ae9b69] xfs: race freeze and fsmap for a while to see if we livelock
      [5e76656346b0] xfs: make sure our default quota warning limits and grace periods survive quotacheck
      [5053ed2ff0a6] xfs: test sunit/swidth updates

Eric Sandeen (5):
      [d4c5b1cabd53] fstests: add _require_sysctl_variable helper
      [fad7fc57f7d2] fstests: test restricted symlinks & hardlinks sysctls
      [6c5ab7590174] fstests: test restricted file access sysctls
      [04f13c4ee3e2] fstests: add _require_mknod
      [e63337b1eda1] fstests: check for unknown flag result in _require_xfs_io_command

Eryu Guan (1):
      [2efe93a3be1f] fstests: renumber tests after merge

Qu Wenruo (2):
      [a297366f5621] btrfs: Add a test for leaking root crash at unmount time
      [b77be1c0ca38] btrfs: Add a test for dead looping balance after balance cancel


Code Diffstat:

 common/rc             |  15 +++++
 tests/btrfs/212       |  85 +++++++++++++++++++++++
 tests/btrfs/212.out   |   2 +
 tests/btrfs/213       |  66 ++++++++++++++++++
 tests/btrfs/213.out   |   2 +
 tests/btrfs/group     |   2 +
 tests/generic/062     |   1 +
 tests/generic/184     |   1 +
 tests/generic/306     |   1 +
 tests/generic/401     |   1 +
 tests/generic/434     |   1 +
 tests/generic/479     |   1 +
 tests/generic/564     |   3 +
 tests/generic/597     | 117 ++++++++++++++++++++++++++++++++
 tests/generic/597.out |  14 ++++
 tests/generic/598     | 128 +++++++++++++++++++++++++++++++++++
 tests/generic/598.out |  28 ++++++++
 tests/generic/group   |   2 +
 tests/overlay/031     |   1 -
 tests/xfs/516         | 182 ++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/xfs/516.out     |   9 +++
 tests/xfs/517         | 108 ++++++++++++++++++++++++++++++
 tests/xfs/517.out     |   4 ++
 tests/xfs/518         |  69 +++++++++++++++++++
 tests/xfs/518.out     |  13 ++++
 tests/xfs/519         |  65 ++++++++++++++++++
 tests/xfs/519.out     |   7 ++
 tests/xfs/group       |   4 ++
 28 files changed, 931 insertions(+), 1 deletion(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2020-05-24 17:06 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=5ecaa97c.1c69fb81.2e77c.a238@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.