#6931: LVM2.2.02.132
-------------------------+------------------------------
Reporter: fo | Owner: pierre.labastie
Type: enhancement | Status: assigned
Priority: normal | Milestone: 7.9
Component: BOOK | Version: SVN
Severity: normal | Resolution:
Keywords: |
-------------------------+------------------------------
Comment (by pierre.labastie):
Thanks to you both for your support. I think I've reached a conclusion for
now. At several places, the tests use the target ''DM_DELAY'' (I/O
delaying target), which I had not selected on some machines, but was
selected on others (the ones with good tests results). The help for this
switch says:
{{{
CONFIG_DM_DELAY:
A target that delays reads and/or writes and can send
them to different devices. Useful for testing.
If unsure, say N.
}}}
Well, using something which is useful for testing when doing tests is not
totally wrong, actually. What is wrong is that the tests are marked
''failed'' when that something is not there...
So you have to select almost all the targets (either as modules or
inline). I select everything except the ones marked "EXPERIMENTAL". Then,
removing ''lvcreate-large-raid.sh'', and ''shell/snapshot-remove-
dmsetup.sh'', and running '''make check_local''' (the -k is not needed), I
get on all machines I have tried:
{{{
228 tests: 148 passed, 47 skipped, 31 broken, 2 failed
}}}
Note that removing the ''Thin provisioning target'' decreases the number
of ''broken'' tests and increases the number of ''skipped'' ones.
Note also that '''make check_local''' runs the same tests as '''make
check''', except that it does not try to run ''ndev-cluster'' tests, which
are all skipped eventually.
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/6931#comment:24>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
