FS/XFS testing framework
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: [GIT PULL] fstests: btrfs changes for for-next v2024.04.03
Date: Wed,  3 Apr 2024 15:24:14 +0800	[thread overview]
Message-ID: <20240403072417.7034-1-anand.jain@oracle.com> (raw)

Zorro,

Please pull this branch, which includes cleanups for background processes
initiated by the testcase upon its exit.

Thank you.

The following changes since commit e72e052d56c3f05e533f4b67056f86931f688368:

  generic: test MADV_POPULATE_READ with IO errors (2024-03-30 15:48:12 +0800)

are available in the Git repository at:

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

for you to fetch changes up to 8aab1f1663031cccb326ffbcb087b81bfb629df8:

  common/btrfs: lookup running processes using pgrep (2024-04-03 15:09:01 +0800)

----------------------------------------------------------------
Anand Jain (1):
      common/btrfs: lookup running processes using pgrep

Filipe Manana (10):
      btrfs: add helper to kill background process running _btrfs_stress_balance
      btrfs/028: use the helper _btrfs_kill_stress_balance_pid
      btrfs/028: removed redundant sync and scratch filesystem unmount
      btrfs: add helper to kill background process running _btrfs_stress_scrub
      btrfs: add helper to kill background process running _btrfs_stress_defrag
      btrfs: add helper to kill background process running _btrfs_stress_remount_compress
      btrfs: add helper to kill background process running _btrfs_stress_replace
      btrfs: add helper to stop background process running _btrfs_stress_subvolume
      btrfs: remove stop file early at _btrfs_stress_subvolume
      btrfs/06[0-9]..07[0-4]: kill all background tasks when test is killed/interrupted

 common/btrfs    | 84 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/btrfs/028 | 16 ++++-------
 tests/btrfs/060 | 33 ++++++++++++++++-------
 tests/btrfs/061 | 30 ++++++++++++++-------
 tests/btrfs/062 | 30 ++++++++++++++-------
 tests/btrfs/063 | 30 ++++++++++++++-------
 tests/btrfs/064 | 30 ++++++++++++++-------
 tests/btrfs/065 | 33 ++++++++++++++++-------
 tests/btrfs/066 | 33 ++++++++++++++++-------
 tests/btrfs/067 | 33 ++++++++++++++++-------
 tests/btrfs/068 | 33 ++++++++++++++++-------
 tests/btrfs/069 | 31 ++++++++++++++-------
 tests/btrfs/070 | 31 ++++++++++++++-------
 tests/btrfs/071 | 31 ++++++++++++++-------
 tests/btrfs/072 | 31 ++++++++++++++-------
 tests/btrfs/073 | 30 ++++++++++++++-------
 tests/btrfs/074 | 30 ++++++++++++++-------
 tests/btrfs/132 |  2 +-
 tests/btrfs/255 |  8 ++----
 19 files changed, 418 insertions(+), 161 deletions(-)

             reply	other threads:[~2024-04-03  7:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03  7:24 Anand Jain [this message]
2024-04-09 14:26 ` [GIT PULL] fstests: btrfs changes for for-next v2024.04.03 David Sterba
2024-04-13 19:28   ` Zorro Lang
2024-04-13 23:13     ` Anand Jain
2024-04-14  7:11       ` Zorro Lang

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