From: Anand Jain <anand.jain@oracle.com>
To: Zorro Lang <zlang@redhat.com>, David Sterba <dsterba@suse.cz>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [GIT PULL] fstests: btrfs changes for for-next v2024.04.03
Date: Sun, 14 Apr 2024 07:13:43 +0800 [thread overview]
Message-ID: <27c469b2-95f3-4232-8b86-1c8527eee314@oracle.com> (raw)
In-Reply-To: <20240413192824.sz4ppx3rmdvcov6i@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On 4/14/24 03:28, Zorro Lang wrote:
> On Tue, Apr 09, 2024 at 04:26:27PM +0200, David Sterba wrote:
>> On Wed, Apr 03, 2024 at 03:24:14PM +0800, Anand Jain wrote:
>>> Zorro,
>>>
>>> Please pull this branch, which includes cleanups for background processes
>>> initiated by the testcase upon its exit.
>>
>> What is the ETA for a pull request to be merged? Not just this one but
>> in general for fstests. I don't see the patches in any of for-next or
>> queued.
>
> I think you might be confused by the subject of this PR, there's not v2024.04.03
> version, and no plan for v2024.04.03.
>
It is the patches which were pending to be pulled as below, and I see
them now in the patches-in-queue branch.
--------
https://github.com/asj/fstests.git staged-20240403
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
--------
Thanks, Anand
> Last fstests release is v2024.03.31, I generally make a new release in ~2 weeks
> (1 week at least, 3 weeks rarely), and each release is nearly on Sunday. Due to
> I have to give the new release a basic test and check the test results at the
> weekend (I have my jobs on workdays), if nothing wrong, I'll push it on my Sunday
> night. That's how I deal with fstests release, please feel free to tell me if you
> have any concern :)
>
> Thanks,
> Zorro
>
>>
>
next prev parent reply other threads:[~2024-04-13 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 7:24 [GIT PULL] fstests: btrfs changes for for-next v2024.04.03 Anand Jain
2024-04-09 14:26 ` David Sterba
2024-04-13 19:28 ` Zorro Lang
2024-04-13 23:13 ` Anand Jain [this message]
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=27c469b2-95f3-4232-8b86-1c8527eee314@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--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