On 09/05/2018 09:15 PM, Xi Ruoyao wrote:
In Coreutils testing
<http://www.linuxfromscratch.org/lfs/build-logs/8.3/i7-5820K/test-logs/122-coreutils-8.30>:
cp-mv-enotsup-xattr.sh: skipped test: failed to create ext2 file system
SKIP: tests/cp/cp-mv-enotsup-xattr.sh
PASS: tests/cp/capability.sh
fiemap_capable_: python missing: assuming not fiemap capable
sparse-fiemap.sh: skipped test: current file system has insufficient FIEMAP
support
SKIP: tests/cp/sparse-fiemap.sh
cross-dev-symlink.sh: skipped test: failed to create ext4 file system
SKIP: tests/cp/cross-dev-symlink.sh
skip-seek-past-dev.sh: skipped test: failed to determine size of /dev/sda4
SKIP: tests/dd/skip-seek-past-dev.sh
problematic-chars.sh: skipped test: failed to create ext2 file system
SKIP: tests/df/problematic-chars.sh
over-mount-device.sh: skipped test: failed to create ext2 file system
SKIP: tests/df/over-mount-device.sh
Several tests are skipped because "failed to create file system" or
"failed to determine size". They should not happen in theory.
The problem here is programs `mkfs`, `fdisk`, etc from Chapter 5
util-linux is in `/tools/sbin`, which is not in $PATH. I don't know
if other testsuites suffer the same problem.
We can add `/tools/sbin` to $PATH in 6.4 (Chroot) so testsuites in
Chapter 6 can use the programs in it.
We can try that, but I'm not really sure how important it is. We run
the tests really as a confidence check of our build. A few skipped
tests are not really important unless we want to do development work on
a specific package. In that case a developer should be doing the work
on a full system, not the partial environment in Chapter 6.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
