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 a0b0287cb747
Date: Mon, 30 Dec 2019 02:28:43 +0800	[thread overview]
Message-ID: <5e08f060.1c69fb81.4707a.c444@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2123 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 btrfs tests and fixes.
Notably, fsstress is able to do btrfs subvolume tests, and you may hit new
failures when testing btrfs. Also, a regression introduced in last update in
generic/386 has been fixed, the test passes on ext4 now.

Many thanks to Filipe Manana, who helped review most of the btrfs updates!

And this is the last update in 2019, happy new year!

Thanks,
Eryu

The new head of the master branch is commit:

a0b0287cb747 btrfs/15[78]: Use proper helper to get both devid and physical offset for corruption

New commits:

Josef Bacik (4):
      [fb769938dcc5] fsstress: add the ability to create/delete subvolumes
      [fd0830929573] fsstress: add the ability to create snapshots
      [f2e567ab172c] fsstress: allow operations to use either a directory or subvol
      [805c6262d5f7] src/fssum: skip subvolumes when building a sum

Qu Wenruo (3):
      [ab76e971702d] common: Use more accurate kernel config for _require_fail_make_request
      [1a27bf14ef8b] btrfs/14[23]: Use proper help to get both devid and physical offset for corruption.
      [a0b0287cb747] btrfs/15[78]: Use proper helper to get both devid and physical offset for corruption

Theodore Ts'o (1):
      [ea726c4a55c9] generic/386: check the correct field from df output


Code Diffstat:

 common/rc              |   2 +-
 configure.ac           |   1 +
 include/builddefs.in   |   1 +
 ltp/Makefile           |   4 +
 ltp/fsstress.c         | 299 +++++++++++++++++++++++++++++++++++++++++--------
 m4/package_libbtrfs.m4 |   5 +
 src/fssum.c            |  11 ++
 tests/btrfs/142        |  52 ++++++---
 tests/btrfs/142.out    |   2 -
 tests/btrfs/143        |  50 ++++++---
 tests/btrfs/143.out    |   2 -
 tests/btrfs/157        |  49 +++++---
 tests/btrfs/157.out    |   4 -
 tests/btrfs/158        |  44 +++++---
 tests/btrfs/158.out    |   4 -
 tests/generic/386      |   6 +-
 16 files changed, 414 insertions(+), 122 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2019-12-29 18:28 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=5e08f060.1c69fb81.4707a.c444@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