Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: zlang@redhat.com
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: [GIT PULL] fstests: btrfs changes for for-next v2024.03.08
Date: Fri,  8 Mar 2024 20:15:32 +0530	[thread overview]
Message-ID: <20240308144537.16995-1-anand.jain@oracle.com> (raw)

Zorro,

Please pull this branch containing bug fixes.
This changes are based on your branch for-next as below.

Thank you.

The following changes since commit 9b6df9a01ac8ee3f28a2a24d71e45792e21b6d48:

  btrfs/016: fix a false alert due to xattrs mismatch (2024-03-01 19:24:16 +0800)

are available in the Git repository at:

  https://github.com/asj/fstests.git staged-20240308

for you to fetch changes up to 9a03e88a04b6cf6e161c8902a3a523ca22601277:

  btrfs: test normal qgroup operations in a compress friendly way (2024-03-08 22:31:51 +0800)

----------------------------------------------------------------
Anand Jain (1):
      common/rc: specify required device size

Filipe Manana (1):
      btrfs: fix grep warning at _require_btrfs_mkfs_uuid_option()

Josef Bacik (8):
      btrfs/011: increase the runtime for replace cancel
      btrfs/012: adjust how we populate the fs to convert
      btrfs/131: don't run with subpage blocksizes
      btrfs/213: make the test more reliable
      btrfs/271: adjust failure condition
      btrfs/287,btrfs/293: filter all btrfs subvolume delete calls
      btrfs/291: remove image file after teardown
      btrfs: test normal qgroup operations in a compress friendly way

 check               |   6 ---
 common/btrfs        |   2 +-
 common/rc           |   9 ++++-
 tests/btrfs/011     |   9 ++++-
 tests/btrfs/012     |  14 ++++---
 tests/btrfs/022     |  86 ++---------------------------------------
 tests/btrfs/131     |   4 ++
 tests/btrfs/213     |  20 +++++-----
 tests/btrfs/271     |  11 +++---
 tests/btrfs/287     |   4 +-
 tests/btrfs/287.out |   2 +-
 tests/btrfs/291     |   2 +-
 tests/btrfs/293     |   6 +--
 tests/btrfs/293.out |   4 +-
 tests/btrfs/320     | 107 ++++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/btrfs/320.out |   2 +
 16 files changed, 164 insertions(+), 124 deletions(-)
 create mode 100755 tests/btrfs/320
 create mode 100644 tests/btrfs/320.out

             reply	other threads:[~2024-03-08 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 14:45 Anand Jain [this message]
2024-03-10  9:40 ` [GIT PULL] fstests: btrfs changes for for-next v2024.03.08 Zorro Lang
2024-03-10 17:08 ` Filipe Manana
2024-03-11  2:01   ` Anand Jain

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=20240308144537.16995-1-anand.jain@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zlang@redhat.com \
    /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