From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-6.9 misc-tests.sh failures
Date: Mon, 10 Jun 2024 14:38:31 -0500 [thread overview]
Message-ID: <35e67c45-b0da-49ff-99e5-8393b93bd2d0@gmail.com> (raw)
failed: /build/btrfs/btrfs-progs-v6.9/btrfs balance start -mconvert=single
-sconvert=single -f /build/btrfs/btrfs-progs-v6.9/tests/mnt
test failed for case 004-shrink-fs
The misc-tests-results.txt gives:
====== RUN CHECK /build/btrfs/btrfs-progs-v6.9/btrfs filesystem resize 8091860992
/build/btrfs/btrfs-progs-v6.9/tests/mnt
Resize device id 1 (/dev/loop0) from 7.54GiB to 7.54GiB
====== RUN CHECK /build/btrfs/btrfs-progs-v6.9/btrfs balance start -mconvert=single
-sconvert=single -f /build/btrfs/btrfs-progs-v6.9/tests/mnt
ERROR: error during balancing '/build/btrfs/btrfs-progs-v6.9/tests/mnt': No space
left on device
There may be more info in syslog - try dmesg | tail
failed: /build/btrfs/btrfs-progs-v6.9/btrfs balance start -mconvert=single
-sconvert=single -f /build/btrfs/btrfs-progs-v6.9/tests/mnt
test failed for case 004-shrink-fs
How much space is needed? On my /build partition:
SOURCE TARGET FSTYPE SIZE USED AVAIL USE%
/dev/nvme0n1p7 /build ext4 245G 141.2G 91.3G 58%
Disabling case 004-shrink-fs the next issue is
====== RUN MUSTFAIL /build/btrfs/btrfs-progs-v6.9/btrfs subvolume delete
/build/btrfs/btrfs-progs-v6.9/tests/mnt/snap1
Delete subvolume 257 (no-commit): '/build/btrfs/btrfs-progs-v6.9/tests/mnt/snap1'
succeeded (unexpected!): /build/btrfs/btrfs-progs-v6.9/btrfs subvolume delete
/build/btrfs/btrfs-progs-v6.9/tests/mnt/snap1
unexpected success: deleting default subvolume by path succeeded
test failed for case 041-subvolume-delete-during-send
I do not have any insight into this issue.
After disabling 041-subvolume-delete-during-send all other tests pass.
-----
Note, the reason we run tests in linuxfromscratch it to give users confidence in the
packages built. We can just disable some tests and label them as known errors,
but it seems that an important package like btrfs should test clean. If the test
failures are something we have done wrong, we would like to fix it.
-- Bruce Dubbs
linuxfromscratch.org
next reply other threads:[~2024-06-10 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 19:38 Bruce Dubbs [this message]
2024-06-10 21:49 ` btrfs-6.9 misc-tests.sh failures 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=35e67c45-b0da-49ff-99e5-8393b93bd2d0@gmail.com \
--to=bruce.dubbs@gmail.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