From: Eryu Guan <guan@eryu.me>
To: fstests@vger.kernel.org
Subject: Re: [ANNOUNCE] fstests: master branch updated to 31f6949f385a
Date: Mon, 26 Oct 2020 14:55:13 +0800 [thread overview]
Message-ID: <20201026065513.GC3853@desktop> (raw)
[Seems this ANNOUNCE didn't hit the list, quote it and send again]
On Sun, Oct 25, 2020 at 07:02:50PM +0800, Eryu Guan wrote:
> 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 normal new test & bug fix update. There're
> two new btrfs tests and one ext4 test, and they should all pass with latest
> 5.9.0+ kernel. The rest of the update is random fixes, the only user-visible
> change is that btrfs now supports setting BTRFS_MKFS_OPTIONS as well to define
> the btrfs mkfs options.
>
> Thanks,
> Eryu
>
> The new head of the master branch is commit:
>
> 31f6949f385a ext4: verify unwritten extent conversion in buff-io
>
> New commits:
>
> Anand Jain (2):
> [0cea5f97ef18] btrfs: add a test case for btrfs seed device delete
> [4504deda8ba7] btrfs/163: replace sprout instead of seed
>
> Filipe Manana (2):
> [2eb35a8594dc] check: fix misspelled variable name for sections
> [a7fdd2e1b1dc] btrfs: add test case for rwf_nowait writes
>
> Goldwyn Rodrigues (1):
> [da60e675f641] common/config: Allow environment defined btrfs mkfs options
>
> Matthew Wilcox (1):
> [2f65e8db375e] generic/127: to exit if any subtest fails
>
> Murphy Zhou (1):
> [85a3354edab0] overlay/073: test with nfs_export being off
>
> Ritesh Harjani (1):
> [31f6949f385a] ext4: verify unwritten extent conversion in buff-io
>
> Yang Xu (1):
> [e944dd5b9df6] generic/402: Drop useless fail message
>
>
> Code Diffstat:
>
> check | 4 +-
> common/config | 3 ++
> tests/btrfs/163 | 25 +++++++---
> tests/btrfs/163.out | 5 +-
> tests/btrfs/225 | 82 ++++++++++++++++++++++++++++++
> tests/btrfs/225.out | 15 ++++++
> tests/btrfs/226 | 140 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> tests/btrfs/226.out | 70 ++++++++++++++++++++++++++
> tests/btrfs/group | 2 +
> tests/ext4/046 | 84 +++++++++++++++++++++++++++++++
> tests/ext4/046.out | 2 +
> tests/ext4/group | 1 +
> tests/generic/127 | 12 ++---
> tests/generic/402 | 2 +-
> tests/overlay/073 | 4 +-
> 15 files changed, 433 insertions(+), 18 deletions(-)
> --
> Eryu Guan
> guan@eryu.me
reply other threads:[~2020-10-26 6:55 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=20201026065513.GC3853@desktop \
--to=guan@eryu.me \
--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