From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs-progs: tests false alerts fixes
Date: Wed, 9 Aug 2023 06:40:40 +0800 [thread overview]
Message-ID: <cover.1691533896.git.wqu@suse.com> (raw)
This is the resent and aggregate version of the fixes I sent but mostly
eaten by the recent vger down time.
Those are small fixes for the false alerts I hit during my local runs.
Most of them are subtle fixes, only the last one is more like an
optimization.
Qu Wenruo (4):
btrfs-progs: tests/mkfs/005: use udevadm settle to avoid false alerts
btrfs-progs: tests/misc/030: do not require v1 cache for the test case
btrfs-progs: tests/misc/046: fix false alerts on write detection
btrfs-progs: tests/misc/058: reduce the space requirement and speed up
the test
tests/misc-tests/030-missing-device-image/test.sh | 8 --------
tests/misc-tests/046-seed-multi-mount/test.sh | 4 +++-
tests/misc-tests/058-replace-start-enqueue/test.sh | 5 ++---
tests/mkfs-tests/005-long-device-name-for-ssd/test.sh | 4 +++-
4 files changed, 8 insertions(+), 13 deletions(-)
--
2.41.0
next reply other threads:[~2023-08-08 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 22:40 Qu Wenruo [this message]
2023-08-08 22:40 ` [PATCH 1/4] btrfs-progs: tests/mkfs/005: use udevadm settle to avoid false alerts Qu Wenruo
2023-08-08 22:40 ` [PATCH 2/4] btrfs-progs: tests/misc/030: do not require v1 cache for the test case Qu Wenruo
2023-08-08 22:40 ` [PATCH 3/4] btrfs-progs: tests/misc/046: fix false alerts on write detection Qu Wenruo
2023-08-08 22:40 ` [PATCH 4/4] btrfs-progs: tests/misc/058: reduce the space requirement and speed up the test Qu Wenruo
2023-08-11 14:53 ` [PATCH 0/4] btrfs-progs: tests false alerts fixes David Sterba
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=cover.1691533896.git.wqu@suse.com \
--to=wqu@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).