From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs-progs: tests: fix false alerts on github CI
Date: Sun, 15 Nov 2026 09:33:19 +1030 [thread overview]
Message-ID: <cover.1794697359.git.wqu@suse.com> (raw)
After the CI workers updated to ubuntu 26.04, there are several new fail tests cases:
- convert/017
There is not enough metadata space to support a convert.
This test relies on both the mkfs.ext4 behavior and kernel ext4 write behavior.
Change the test case to skip the run if there is not enough space left.
- mkfs/037
There is no '/usr/lib/lib*` files anymore there on ubuntu 26.04.
Use generated data instead.
Qu Wenruo (2):
btrfs-progs: tests: fix false alerts on convert/017
btrfs-progs: tests: fix github CI failure on mkfs/037
tests/convert-tests/017-fs-near-full/test.sh | 12 +++++--
.../mkfs-tests/037-basic-compression/test.sh | 31 +++++++++----------
2 files changed, 24 insertions(+), 19 deletions(-)
--
2.56.0
next reply other threads:[~2026-11-14 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 23:03 Qu Wenruo [this message]
2026-11-14 23:03 ` [PATCH 1/2] btrfs-progs: tests: fix false alerts on convert/017 Qu Wenruo
2026-11-14 23:03 ` [PATCH 2/2] btrfs-progs: tests: fix github CI failure on mkfs/037 Qu Wenruo
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.1794697359.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