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 4cabd42a78d2
Date: Sun, 08 Apr 2018 16:06:20 +0800	[thread overview]
Message-ID: <5ac9cd81.caa0620a.d20bb.d992@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1423 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 mainly pulls in the new log-writes test
from Qu Wenruo, which checks for fs consistency after each FUA write using
dm-logwrites. Please note that the new test (generic/482) fails on XFS and ext4
sometimes, not sure if it's a filesystem issue or a dm-logwrites issue yet.

New failures I've noticed in this update
- generic/482 sometimes fails on XFS and ext4, please see above 

Thanks,
Eryu

The new head of the master branch is commit:

4cabd42a78d2 generic: Check the fs after each FUA writes

New commits:

Benjamin Coddington (1):
      [43374a62325e] common/rc: improve checks for YP/NIS

Qu Wenruo (3):
      [00b6ad8f265e] log-writes: Add support to output human readable flags
      [5311ba16c6e8] log-writes: Add support for METADATA flag
      [4cabd42a78d2] generic: Check the fs after each FUA writes


Code Diffstat:

 common/dmlogwrites          |  56 +++++++++++++++++++++++
 common/rc                   |   3 +-
 src/log-writes/log-writes.c |  71 ++++++++++++++++++++++++++---
 src/log-writes/log-writes.h |   9 ++--
 tests/generic/482           | 108 ++++++++++++++++++++++++++++++++++++++++++++
 tests/generic/482.out       |   2 +
 tests/generic/group         |   1 +
 7 files changed, 238 insertions(+), 12 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2018-04-08  8: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=5ac9cd81.caa0620a.d20bb.d992@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