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 bb8de58ca1d0
Date: Sun, 13 May 2018 20:29:57 +0800	[thread overview]
Message-ID: <5af82fc8.1c69fb81.4f68f.3d7e@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2519 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, there're 5 new tests
and several cleanups and improvements, e.g. removing unused code, removing
'dangerous' group from a few tests. 

But there should be no new failures introduced by this update.

Thanks,
Eryu

The new head of the master branch is commit:

bb8de58ca1d0 btrfs: add test for seeing unseen fsync errors on newly open files

New commits:

Amir Goldstein (4):
      [12a986fe876d] overlay/049: update fix commit id
      [5509684db3b7] overlay: test multiple origin references to the same lower file
      [c29a70330fdf] common/rc: decouple xfs_io flink check from xfs_io -T check
      [b3c907888d56] generic/{159,160}: require chattr instead of lsattr

Darrick J. Wong (1):
      [331edc6af659] xfs: checkbashisms in all script files

Dave Chinner (3):
      [46199319f61f] fstests: remove old electric fence support
      [f3851ad630ba] fstests: many dangerous+auto tests are not dangerous anymore
      [272ddcdd191e] xfs: test inobt/on disk free state mismatches

Jeff Layton (2):
      [22a147a1ad7b] generic: test for seeing unseen fsync errors on newly open files
      [bb8de58ca1d0] btrfs: add test for seeing unseen fsync errors on newly open files


Code Diffstat:

 check                 |   7 +---
 common/log            |   1 -
 common/rc             |  38 ++++++------------
 common/xfs            |   9 ++---
 soak                  |   6 +--
 tests/btrfs/058       |   4 +-
 tests/btrfs/160       | 105 ++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/btrfs/160.out   |   5 +++
 tests/btrfs/group     |   1 +
 tests/generic/004     |   1 +
 tests/generic/159     |   2 +-
 tests/generic/160     |   2 +-
 tests/generic/389     |   1 +
 tests/generic/487     | 104 +++++++++++++++++++++++++++++++++++++++++++++++++
 tests/generic/487.out |   5 +++
 tests/generic/group   |  15 ++++----
 tests/overlay/049     |   4 +-
 tests/overlay/059     | 105 ++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/overlay/059.out |   2 +
 tests/overlay/group   |   1 +
 tests/xfs/132         |  73 +++++++++++++++++++++++++++++++++++
 tests/xfs/132.out     |  26 +++++++++++++
 tests/xfs/446         |  52 +++++++++++++++++++++++++
 tests/xfs/446.out     |   2 +
 tests/xfs/group       |  18 +++++----
 tools/auto-qa         |   1 -
 26 files changed, 527 insertions(+), 63 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2018-05-13 12:30 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=5af82fc8.1c69fb81.4f68f.3d7e@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