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 60300eb6e150
Date: Sat, 19 May 2018 22:23:45 +0800	[thread overview]
Message-ID: <5b003374.1c69fb81.dc914.ea23@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2686 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 contains 5 new tests that are for generic,
and xfs, along with some quota test fixes for ext2/3.

New failures I've noticed in this update:
- generic/44[89] currently fails on btrfs
- generic/490 fails on ext3, and ext2 when driven by ext4 module
- generic/491 triggers WARNING on ext4

Thanks,
Eryu

The new head of the master branch is commit:

60300eb6e150 generic/459: use xfs_freeze instead of fsfreeze

New commits:

Amir Goldstein (4):
      [e401bc28c1ba] generic/484: add missing _require_test_program
      [ab4c48e3aee4] fstests: define and use TIMEOUT_PROG
      [5018cd1c0f9f] generic: test first read with freeze right after mount
      [60300eb6e150] generic/459: use xfs_freeze instead of fsfreeze

Dave Chinner (1):
      [5fc65da0a6ff] xfs: test mount vs superblock shrinker races

Filipe Manana (1):
      [fd0607faf234] generic: test for fsync of file with xattrs

Jan Kara (3):
      [5761a6eaade2] generic: Add SEEK_DATA tests for offsets in the middle of holes
      [b2bffe5c77d6] common/quota: Make project quota handling work for ext2 & ext3
      [3d112df8bdc3] common/quota: Fix _qmount_options for ext4 journalled quotas

Omar Sandoval (1):
      [5c19a58f7d99] btrfs: test ENOSPC caused by many orphan items

Xiao Yang (1):
      [287b2e05b527] generic/486: Get rid of the redundant error=%d printing

Zorro Lang (1):
      [a82e9464ddfb] xfs: skip growfs test on large device


Code Diffstat:

 common/config           |  1 +
 common/quota            | 10 +++---
 src/attr_replace_test.c |  2 +-
 src/seek_sanity_test.c  | 71 ++++++++++++++++++++++++++++++++++++++++
 tests/generic/297       |  4 +--
 tests/generic/298       |  4 +--
 tests/generic/459       |  6 ++--
 tests/generic/479       |  0
 tests/generic/484       |  1 +
 tests/generic/488       | 62 +++++++++++++++++++++++++++++++++++
 tests/generic/488.out   |  2 ++
 tests/generic/489       | 86 +++++++++++++++++++++++++++++++++++++++++++++++++
 tests/generic/489.out   | 11 +++++++
 tests/generic/490       | 60 ++++++++++++++++++++++++++++++++++
 tests/generic/490.out   |  1 +
 tests/generic/491       | 75 ++++++++++++++++++++++++++++++++++++++++++
 tests/generic/491.out   |  2 ++
 tests/generic/group     |  4 +++
 tests/xfs/002           |  1 +
 tests/xfs/127           |  1 +
 tests/xfs/233           |  1 +
 tests/xfs/447           | 72 +++++++++++++++++++++++++++++++++++++++++
 tests/xfs/447.out       |  2 ++
 tests/xfs/group         |  1 +
 24 files changed, 468 insertions(+), 12 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2018-05-19 14:23 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=5b003374.1c69fb81.dc914.ea23@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