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 623b4ea4082b
Date: Sun, 04 Jul 2021 21:22:15 +0800	[thread overview]
Message-ID: <60e1b60b.1c69fb81.b47e1.7376@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2057 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 normal bugfix update, with only one new test,
which should pass on all filesystems.

And the 'auto generated group file rework' seems stable, it didn't introduce
any regression so far, the only issue reported was generic/019 failure, which
was exposed not caused by the rework. But bugs may still hide somewhere, please
help report and/or fix bugs, as always, if you hit any.

Thanks,
Eryu

The new head of the master branch is commit:

623b4ea4082b overlay/Makefile: Use the unified name rules

New commits:

Anju T Sudhakar (1):
      [3be0233fbbcf] xfs/504: Add scratch_mount before checking for xfs_scrub unicode support

Darrick J. Wong (1):
      [c9419e671d0c] tools: make convert-group ignore converted test files

Dave Chinner (1):
      [35ff42b1dc1e] generic/019: fix test cleanup

Jeff Layton (1):
      [80b8fe47d013] generic: ensure that page is properly filled before write

Sun Ke (3):
      [7f17fee84a88] generic/042: make a bigger img for f2fs
      [9e31513f5fbd] generic/103: special left calculation for f2fs
      [c360cd10a1b8] generic/260: f2fs is also special

Theodore Ts'o (1):
      [a9e50808a843] check: exit with exit code 1 after printing the usage message

Yang Xu (2):
      [23e3bf7e28be] Makefile: fix bug when running make install under tests/* directory
      [623b4ea4082b] overlay/Makefile: Use the unified name rules


Code Diffstat:

 Makefile               |  3 ++-
 check                  |  2 +-
 include/builddefs.in   |  2 +-
 tests/generic/019      |  2 --
 tests/generic/042      |  6 ++++--
 tests/generic/103      | 10 +++++++++-
 tests/generic/260      | 10 ++++++++--
 tests/generic/639      | 39 +++++++++++++++++++++++++++++++++++++++
 tests/generic/639.out  |  5 +++++
 tests/overlay/Makefile |  4 ++--
 tests/xfs/504          |  3 +++
 tools/convert-group    |  2 ++
 12 files changed, 76 insertions(+), 12 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2021-07-04 13:22 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=60e1b60b.1c69fb81.b47e1.7376@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