tests: remove loop devices from lsblk bcachefs dump

The loop device infrastructure does not support sysfs dump-based data.
When lsblk runs with --sysroot, the ignore_empty() function calls
loopdev_has_backing_file() which operates on the real /dev/loopN
device rather than the sysroot data. This causes host-dependent test
results -- if the CI machine has a loop device with a backing file,
the device appears in the output despite having size 0 in the dump.

Remove loop0 and loop1 entries from the multi-devs-bcachefs sysfs
dump to avoid this false positive.

Signed-off-by: Karel Zak <kzak@redhat.com>

diff --git a/tests/ts/lsblk/dumps/multi-devs-bcachefs.tar.xz b/tests/ts/lsblk/dumps/multi-devs-bcachefs.tar.xz
index 1f69e88427e98b493772793640b49604d5a52ff4..8a0389f47b1cc134957d9d6c1ce73f8873c9be85 100644 (file)
Binary files a/tests/ts/lsblk/dumps/multi-devs-bcachefs.tar.xz and b/tests/ts/lsblk/dumps/multi-devs-bcachefs.tar.xz differ